5

When I mount a server file system that is located in a local network over nfs on my laptop, the processes interacting with the filesystem freeze / hang up whenever the network connection is lost. The file explorer (Dolphin) window freezes, and through the terminal I cannot display the contents of the directory that contains the mount point. Trying to sudo umount the folder won't work.

In my case, I use sudo mount -t nfs 192.168.1.100:/elrudi /home/elrudi/nas. I can still cd to any location, but when I try to ls the contents of /home/elrudi, the terminal window hangs. All I can do is force-close the affected windows. When opening a new dolphin/terminal window, the problem persists.

Some observations:

  • If the network connection gets restored, the problem goes away - most of the times. Curiously, dolphin seems to need a little kick to unfreeze, which can be administered by lsing /home/elrudi in a terminal.
  • If the network connection cannot be restored, however, such as when it is out of reach, there is nothing that can be done (that I know of). Even rebooting the system is not an option, as it hangs at the 'final' screen ('ubuntu' with process progress dots that light up one after the other).

I'd like to know if there is a way to make a more robust mount, or if there is something I can do to make the system responsive again.

Thanks!

ElRudi
  • 299

1 Answers1

0

Did you try the answers in this former post:

How to unmount NFS when server is gone?

I usually do not use static mounts to NFS shares, but rather install autofs and use softlinks like (in your case)

ln -s /net/192.168.1.100/elrudi /home/elrudi/nas

This will mount the share only when used, and umount after a while.

ridgy
  • 2,516