[Bug 1157171] Re: NFS mounts in /etc/fstab fail

Tue Jan 14 07:25:07 UTC 2014

This bug was fixed in the package nfs-utils - 1:1.2.8-5ubuntu1

---------------
nfs-utils (1:1.2.8-5ubuntu1) trusty; urgency=medium

  * Merge from Debian unstable, remaining changes:
    - debian/nfs-common.{statd,statd-mounting,gssd,idmapd}.upstart,
      debian/control, debian/nfs-common.{preinst,postinst,prerm,postrm},
      debian/rules: drop nfs-common init script in favor of upstart jobs.
    - Depend on rpcbind (>= 0.2.0-6ubuntu1) for upstart support.
    - Depend on mountall (>= 2.41) to avoid deadlocks on boot.
    - debian/nfs-common.default: always start idmapd automatically; drop
      the configuration option.
    - nfs-kernel-server.init: Unmount nfsd fs when init script stops
    - Allow issuing options to rpc.nfsd
    - Add "-e" (ticket expiry is error) option to rpc.gssd to prevent hangs
      due to EKEYEXPIRED error from kernel on ticket expiry.
  * Dropped changes, included in Debian:
    - Move /var/lib/nfs/rpc_pipefs to /run/rpc_pipefs.  This does not belong
      in /var/lib.
    - debian/nfs-kernel-server.postinst: don't call "invoke-rc.d nfs-common"
      in the postinst, this is redundant anyway and the nfs-common init script
      is gone now.

nfs-utils (1:1.2.8-5) unstable; urgency=medium

  [ Ben Hutchings ]
  * Remove Luk Claes from uploaders (Closes: #723602)

  [ Steve Langasek ]
  * Migrate the rpc_pipefs mount out of /var/lib to /run, to better
    support /var on NFS.
  * Don't start the nfs-common init script from the nfs-kernel-server
    maintainer script, this is entirely redundant.
  * debian/patches/21-no-more-var-run.patch: PID files should be in
    /run, not /var/run.
    Closes LP: #1157171.
 -- Steve Langasek <steve.langasek at ubuntu.com>   Mon, 13 Jan 2014 21:13:11 -0800

** Changed in: nfs-utils (Ubuntu)
       Status: Triaged => Fix Released

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

Title:
  NFS mounts in /etc/fstab fail

Status in “nfs-utils” package in Ubuntu:
  Fix Released

Bug description:

  I have a bunch of NFS mounts in fstab on some of my webservers. These mount perfectly well if done manually after the boot, but if I do them automatically at boot time, they cause the server to fail to boot properly.

  If I comment them out of fstab, then the server reboots successfully
  every time.

  I've tried hostnames and IP addresses in /etc/fstab, but neither work.

  Example fstab entry:
  10.0.41.14:/mnt/beast/pgw /var/www/pgw/docs nfs ro,rsize=32768,hard,intr,nfsvers=3,udp,noatime,nodev,async,_netdev 0 0

  I'm using static networking in /etc/network/interfaces:
  auto eth0
  iface eth0 inet static
          address 10.0.41.17
          netmask 255.255.255.0
          network 10.0.41.0
          broadcast 10.0.41.255
          gateway 10.0.41.1
          dns-nameservers 10.0.0.2
          dns-search int.xxxxxxx.co.uk 

  The dmesg log  looks as follows: (I've pruned out most of the boot messages)
  [    1.257789] udevd[81]: starting version 175
  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
  [    1.404157] Refined TSC clocksource calibration: 2593.390 MHz.
  [    1.424141] usb 1-1: new full-speed USB device number 2 using uhci_hcd
  Begin: Running /scripts/local-premount ... done.
  [    1.653148] EXT4-fs (vda1): INFO: recovery required on readonly filesystem
  [    1.656874] EXT4-fs (vda1): write access will be enabled during recovery
  [    1.734688] FDC 0 is a S82078B
  [    1.817756] EXT4-fs (vda1): recovery complete
  [    1.822182] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
  Begin: Running /scripts/local-bottom ... done.
  done.
  Begin: Running /scripts/init-bottom ... done.
  [    2.898556] EXT4-fs (vda1): re-mounted. Opts: (null)
  rpcbind: Cannot open '/run/rpcbind/rpcbind.xdr' file for reading, errno 2 (No such file or directory)
  rpcbind: Cannot open '/run/rpcbind/portmap.xdr' file for reading, errno 2 (No such file or directory)
  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: Network is unreachable
  mountall: mount /var/www/tecom/docs [345] terminated with status 32
  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: Network is unreachable
  mountall: mount /var/www/theatrepeople/docs [350] terminated with status 32
  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: Network is unreachable
  mountall: mount /var/www/eolts/docs [337] terminated with status 32
  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: Network is unreachable
  mountall: mount /mnt [341] terminated with status 32
  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: Network is unreachable
  mountall: mount /var/www/cbolds/docs [400] terminated with status 32
  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: Network is unreachable
  mountall: mount /var/www/pgw/docs [339] terminated with status 32

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