[Bug 504224] Re: NFS mounts at boot time prevent boot or print spurious errors

[Steve Langasek]

** Changed in: mountall (Ubuntu)
     Assignee: susmita ghosh (surja-bi-das) => (unassigned)

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

Title:
  NFS mounts at boot time prevent boot or print spurious errors

Status in “mountall” package in Ubuntu:
  Fix Released
Status in “mountall” source package in Lucid:
  Fix Released

Bug description:
  Binary package hint: mountall

  karmic: mountall 1.0

  When mounting NFS shares at boot, the first mount attempt usually
  fails since rpc or portmap are not running, or the network itself is
  not up yet.

  These errors appear although the filesystem will be mounted
  successfully later on, so the user cannot distinguish them from "real"
  mount failures that need intervention by the admin.

  Even worse, when the NFS mounts happen to be for a mountpoint that
  mountall considers essential for boot (like /home), the user is
  dropped to an emergency shell and system refuses to boot.

  A temporary workaround is to add "nobootwait" for the affected
  mountpoints, but this causes the system to continue booting even if
  the mountpoint is not available when the network is set up correctly,
  i.e. if there is a real problem with the NFS server.

  Proposed fix:

  mountall should not try to mount any network file systems when called
  the first time. Only when the network is up and mountall receives
  SIGUSR1 it should try to do so. If this does not work at *that* point,
  mountall should print an error (and stop the boot for essential mount
  points) as before.

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