Actually I have misinterpreted the swedish terms, my system has been suspended when I see the symptoms.
I have checked hibernation also, it seems to be the same problem. But hibernation is not an option after inactivity.
I also wrote firefox when it really was thunderbird that I meant.
Further investigations show that it is automount that fails when :
1. a file is opened for writing on a nfs-mounted volume that autofs mounts
2. autofs unmount the nfs directory after five minutes of inactivity, AND
3. the system is automatically suspended after ten minutes of inactivity
After resuming activity it is impossible to access the volume on the server
To reproduce:
cat > /path/to/file/on/automounted/nfs-dir/file.txt
write some text
wait for the system to suspend (setting in the power management, I chose ten minutes)
Activate the system again and try to access the automounted volume
Actually I have misinterpreted the swedish terms, my system has been suspended when I see the symptoms.
I have checked hibernation also, it seems to be the same problem. But hibernation is not an option after inactivity.
I also wrote firefox when it really was thunderbird that I meant.
Further investigations show that it is automount that fails when :
1. a file is opened for writing on a nfs-mounted volume that autofs mounts
2. autofs unmount the nfs directory after five minutes of inactivity, AND
3. the system is automatically suspended after ten minutes of inactivity
After resuming activity it is impossible to access the volume on the server
To reproduce: file/on/ automounted/ nfs-dir/ file.txt
cat > /path/to/
write some text
wait for the system to suspend (setting in the power management, I chose ten minutes)
Activate the system again and try to access the automounted volume