[Bug 46516] Re: NFSv4 mounts often missing after boot

[Torsten Bronger]

I see this happen on Natty.  In one of five boot processes, an nfs4
entry in /etc/fstab seems to be ignored.

Should this be re-opened or should I file a separate bug?

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

Title:
  NFSv4 mounts often missing after boot

Status in “ifupdown” package in Ubuntu:
  Invalid
Status in “sysvinit” package in Ubuntu:
  Fix Released

Bug description:
  (This bug was originally reported as Bug #46145 and mistakenly marked
  as a duplicate of Bug #44836. Since there is no option to unmake a bug
  duplicate, I resubmit this as a seperate bug. ).

  Depending on the relative order of NFSv3 and NFSv4 mounts in fstab,
  NFSv4 mounts are often not made on boot. The NFSv4 mounts are missing
  from the filesystem and /proc/mounts, not just from mtab.

  After boot:

  pieter at danae:~$ grep : /etc/fstab
  # /etc/fstab: static file system information.
  repo:/aegis /aegis nfs4 rw,rsize=32768,wsize=32768,defaults 0 0
  pixar:/net/pixar /net/pixar nfs rw,tcp,rsize=32768,wsize=32768,defaults 0 0

  pieter at danae:~$ grep : /proc/mounts
  pixar:/net/pixar /net/pixar nfs rw,v3,rsize=32768,wsize=32768,hard,lock,proto=tcp,addr=pixar 0 0

  pieter at danae:~$ sudo mount -a
  pieter at danae:~$ grep : /proc/mounts
  pixar:/net/pixar /net/pixar nfs rw,v3,rsize=32768,wsize=32768,hard,lock,proto=tcp,addr=pixar 0 0
  repo:/aegis /aegis nfs4 rw,v4,rsize=32768,wsize=32768,hard,intr,lock,proto=tcp,addr=repo 0 0

  But if I re-order the NFSv4 mount after the NFSv3 mount, it *is*
  mounted on boot.

  There is an element of nondeterminacy, because on rare occasions the
  NFSv4 mounts *were* made on boot with the original order of fstab.

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