[Bug 1299225] Re: stale nfs file handle blocks shutdown

[Paul Abrahams]

I can suggest the outline of a fix, but I don't have enough system
knowledge to provide the actual code.

What's needed is a script in one of the /etc/rc.d files that checks all
mounted filesystems to see if they are remote.  If a filesystem is
remote, then it is forcibly unmounted.  This script should be positioned
so that it is executed before the networks are shut down and before the
general unmounting.

I'm not sure about the best criterion for choosing the filesystems to be
unmounted in this way.  It might be better to see what device the root
filesystem is on and unmount everything but the ones on that device.

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

Title:
  stale nfs file handle blocks shutdown

Status in “upstart” package in Ubuntu:
  New

Bug description:
  I'm running a fully updated Kubuntu 13.10 on a 64-bit Lenovo Z58
  laptop.  When I shut down, the shutdown process gets stuck with the
  message "stale nfs file handle".  The system just sits there
  thereafter.  I know what's going on but I don't know what to do about
  it, and a system fix is clearly needed.

  I have a mounted remote nfs file system.  At shutdown, the network
  shuts down and leaves the connection stranded before the file system
  can be unmounted.  This problem has been reported already in
  connection with cifs but not, as far as I know, in connection with
  nfs.

  What's needed is a check of mounted file systems before the network is
  shut down.  Any remote file system, whether cifs or nfs, should then
  be unmounted.   Only after the unmount is confirmed can the shutdown
  process continue.  I don't have enough system knowledge to implement
  this myself, or I would.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1299225/+subscriptions