NFSv4 mounts often missing after boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
sysvinit (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
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@danae:~$ grep : /etc/fstab
# /etc/fstab: static file system information.
repo:/aegis /aegis nfs4 rw,rsize=
pixar:/net/pixar /net/pixar nfs rw,tcp,
pieter@danae:~$ grep : /proc/mounts
pixar:/net/pixar /net/pixar nfs rw,v3,rsize=
pieter@danae:~$ sudo mount -a
pieter@danae:~$ grep : /proc/mounts
pixar:/net/pixar /net/pixar nfs rw,v3,rsize=
repo:/aegis /aegis nfs4 rw,v4,rsize=
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.
Related branches
Changed in sysvinit: | |
assignee: | nobody → keybuk |
Changed in sysvinit: | |
assignee: | keybuk → nobody |
You may change the duplicate status of a bug by clicking
"Mark as duplicate" in the left-hand menu.