You are not logged in.
I have a drive connected to my router, shared with NFS, and a laptop running Arch Linux using a wifi connection.
If I get a connection loss while some program is reading from the NFS, or simply disconnect and type "ls /path/to/NFS", that ls will hang of course, but also I can't stop the nfs daemon:
$ sudo /etc/rc.d/netfs stop
:: Unmounting Network Filesystems [BUSY]
umount.nfs: /media/NFS-delt: device is busy [FAIL]nor will my laptop suspend. If I reconnect and let whatever process is looking for the nfs finish, I get to suspend (even dismount the nfs).
Is there a way to make this more "robust"? Why can't the "netfs stop" make ls let go of the NFS?
Last edited by unhammer (2011-12-11 00:05:29)
Offline
on a related note, rsync-ing to the NFS makes my computer intermittently really unresponsive. If I kill the rsync process, the computer more or less freezes (or, just runs as slow as to make no difference; I can sudo reboot and it says "going down" and nothing happens and I end up hard rebooting)
Offline
You must understand options "soft" and "hard" to mount nfs file system. In this happens try "mount -t nfs -o soft,timeo=5,retry=5 ..." parameters to mount net disk.
Offline
You must understand options "soft" and "hard" to mount nfs file system. In this happens try "mount -t nfs -o soft,timeo=5,retry=5 ..." parameters to mount net disk.
Thanks! That solved the problem with suspending ![]()
(The rsync problem remains though – here the connection is constantly up, but the computer just becomes very unresponsive, and I don't want to soft mount when I'm making backups - but I guess that's for another thread.)
Offline