[Bug 610863] Re: statd job starts before service is listening

[Launchpad Bug Tracker]

** Changed in: nfs-utils (Ubuntu)
       Status: New => Confirmed

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

Title:
  statd job starts before service is listening

Status in “nfs-utils” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nfs-common
  nfs-common version:  1:1.2.0-4ubuntu4

  On my Lucid system with latest updates, NFS filesystems sometimes fail
  to mount successfully at boot.

  Steps to reproduce:
  1. In /etc/fstab, add an entry of the form:
  <nfs-server>:<share>    <mountpoint>    nfs    _netdev   0  0
  2. Reboot a number of times

  Expected results:
  The NFS filesystem should be mounted on every boot

  Actual results:
  Occasionally the NFS mount fails and messages of the following form are logged in /var/log/boot.log:
  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 <mountpoint> [<pid>] terminated with status 32

  After a boot where the NFS mounts fail, the mountall process is still running on login. Running:
  kill -USR1 $(pidof mountall)
  will then mount the missing filesystems sucessfully.

  It is also possible to observe the problem without rebooting as
  follows.

  Steps to reproduce:
  Run the following shell loop, after setting $nfs_server, $share and $mntpt to suitable values

  i=0
  while (( i < 100 ))
  do
      stop statd
      start statd
      mount.nfs $nfs_server:$share $mntpt
      umount $mntpt
      (( i++ ))
  done

  Expected results:
  The NFS filesystem should be mounted on every iteration of the loop

  Actual results:
  Occasionally the NFS mount fails and the following messages are output:

  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.
  mount.nfs: an incorrect mount option was specified
  umount: <mountpoint> not mounted

  The symptoms are very similar to this bug back in Karmic:
  https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/445181

  ---
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  NonfreeKernelModules: nvidia
  Package: nfs-common 1:1.2.0-4ubuntu4
  PackageArchitecture: i386
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_AU.UTF-8
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic-pae 2.6.32.15+drm33.5
  Tags: lucid
  Uname: Linux 2.6.32-23-generic-pae i686
  UserGroups:

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