I'm still seeing this problem on a fully updated Natty. My nfs mount
occasionally succeeds at boot, but most of the time it doesn't. After
editing /etc/init/mountall.conf to log the mountall --debug output, I
see these messages in the log:
mounting /myremotedir
spawn: mount -t nfs -o rw,intr,retrans=180,async,noatime,nodiratime
10.0.95.4:/myremotedir /myremotedir
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: an incorrect mount option was specified
mountall: mount /myremotedir [896] terminated with status 32
When the mount fails, "status statd" reports that statd is running,
which makes me think there is still a race condition here.
I'm not sure if it's relevant, but the 10.0.95.x network is reachable
via eth1, not eth0.
I see a lot of "fix released" notes on this bug report. Has the fix
made it in to the Natty release repositories yet? If so, it looks to me
like the fix needs some work.
** Also affects: mountall (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/525154
Title:
mountall for /var races with rpc.statd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/525154/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
