statd is "start on (started portmap or mount TYPE=nfs)"
portmap is "start on (local-filesystems and net-device-up IFACE=lo)"
and the statd job tries to start portmap if it's not already running.
So the only possible race conditions I see here are if
- mount TYPE=nfs is emitted before all the local filesystems are mounted
- mount TYPE=nfs is emitted before lo is configured, and this causes portmap
to fail
- /var is on a network filesystem *other* than NFS (if it's on NFS, then this
can't really be solved, you just get a deadlock if you try)
Can you post your fstab, so I can better understand which of these cases
applies? (I'm not sure it's fixable anyway with current upstart, but at
least we'll know what we're dealing with)
** Changed in: nfs-utils (Ubuntu)
Status: New => Incomplete
--
mountall for /var races with rpc.statd
https://bugs.launchpad.net/bugs/525154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
