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

Joe Warren-Meeks joe.warren.meeks at gmail.com
Thu Mar 21 12:42:19 UTC 2013


Sorry for the delay in response, and for misassigning it.

joe at w1:~$ dpkg -l |grep nfs-common
ii  nfs-common                       1:1.2.5-3ubuntu3.1           NFS support files common to client and server

I'm running Ubuntu precise (12.04.2 LTS)

root at w1:/var/log/upstart# cat statd.log
UPSTART_EVENTS = local-filesystems started
portmap-wait stop/waiting

Seems normal

And no mounting logs.

It looks to be a race condition at startup. I think it's trying to mount
the filesystems before the network and statd have started up and then
hangs at the "Press blah to continue" dialogue. That would explain the
statd not running and the mount.nfs: Network is unreachable entries.

If I remove the entries from fstab and add them into /etc/rc.local then
everything works fine, which would lend some creedence to the theory.

Note that I have put _netdev in the fstab line, which should make mount
wait until the network is available.

Let me know if there is anything I can do to help?

 -- joe.

-- 
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:
  Incomplete

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




More information about the foundations-bugs mailing list