[Bug 547139] Re: mountall tries to mount NFS filesystem before statd starts, generating a non-fatal warning

[Steve Langasek]

** Summary changed:

- mountall tries to mount NFS filesystem before statd starts
+ mountall tries to mount NFS filesystem before statd starts, generating a non-fatal warning

-- 
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/547139

Title:
  mountall tries to mount NFS filesystem before statd starts, generating
  a non-fatal warning

Status in “mountall” package in Ubuntu:
  Invalid
Status in “nfs-utils” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: mountall

  mountall sometimes tries to mount NFS filesystems before rpc.statd has
  started.  When this happens, you get an error on the console like
  this:

  mount.nfs: rpc.statd is not running but is required for remote locking.
  mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
  mountall: mount /net [402] terminated with status 32
  mountall: Filesystem could not be mounted: /net

  It seems the problem is that the statd upstart job is started on
  "mounting TYPE=nfs", but mountall doesn't wait until statd is started
  before attempting the mount.  This becomes a race condition.  If statd
  may or may not be started by the time the mount is attempted.  It's
  easy to expose the race condition by adding a "sleep 1" immediately
  before the "exec rpc.statd" in /etc/init/statd.conf.

  Eventually the nfs filesystem does get mounted (looks like there is
  some retry behavior), but it does result in errors being printed about
  failed mount attempts.

  version info:

  Description:    Ubuntu lucid (development branch)
  Release:        10.04

  mountall 2.8
  nfs-common 1:1.2.0-4ubuntu4

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