statd does not start when /usr is mounted on a separate volume
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nfs-utils (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS v3 volumes.
This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/
I suggest the following fix:
in /etc/init/
start on ((started portmap and local-filesystems) or mounting TYPE=nfs)
(was: start on (started portmap or mounting TYPE=nfs)
On my computer this fixes the issue, nevertheless I am not sure whether this will suit all cases.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nfs-common 1:1.2.0-4ubuntu4
ProcVersionSign
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Apr 21 00:52:06 2010
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: nfs-utils
| Aurélien Begel (pcrider-gmail) wrote | #1 |
| description: | updated |
| description: | updated |
| Aurélien Begel (pcrider-gmail) wrote | #2 |
| Steve Langasek (vorlon) wrote | #3 |
| Steve Langasek (vorlon) wrote | #4 |
I think the bug may be related to a recent change in portmap: indeed until recently portmap did start on "local-
portmap (6.0.0-1ubuntu2) lucid; urgency=low
* portmap should start on virtual-
it only ever writes to /var/run; this should break the circular dependency
between portmap and mountall when the root filesystem is on NFS.
LP: #537133
-- Steve Langasek <email address hidden> Sat, 17 Apr 2010 01:43:55 +0000
In my bug description I said this was linked to /usr mounted on a separate volume, but this could also happen when /var is mounted on a separate volume, see LP #525154.