[Bug 412351] Re: nfs server stand-by cause client hang

[John Gilmore]

When mounting with the "intr" option, you have to interrupt a stalled
program (using Control-C in a terminal, for example) in order to get it
to stop trying to access the server.  If you instead mount with the
"soft" option, NFS accesses will eventually time out without needing to
be interrupted (but you may lose data if you were writing to the NFS
filesystem -- the written data will not get saved anywhere because the
server isn't responding.)  When the server is hung, you should be able
to unmount the server's filesystem using the -l (lazy) option (umount -l
/opt/user1) to avoid future hangs.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/412351

Title:
  nfs server stand-by cause client hang

Status in nfs-utils package in Ubuntu:
  New

Bug description:
  I have two computers at home, both running Ubuntu. One of the computers shares a folder to the other via nfs. On the client side, I mounted the drive by the following line in fstab:
   192.168.1.2:/home/user1/share /opt/user1 nfs rsize=8192,wsize=8192,timeo=14,intr,rw

  however, I found when the server becomes offline after mounting, the client side will have a lot of troubles, for example:
  1. "df" takes forever to complete ("strace df" stalls at the nfs folder)
  2. client computer is unable to suspend
  3. file explorer (thunar) can not open any folder.

  Expected behavior: system should be able to suspend, or browse files
  if the connection to nfs server is timed out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/412351/+subscriptions