I think the bug may be related to a recent change in portmap: indeed until recently portmap did start on "local-filesystems", so /usr (and /var, etc.) was mounted before portmap starts, and statd starts after portmap, so statd could start properly.
portmap (6.0.0-1ubuntu2) lucid; urgency=low
* portmap should start on virtual-filesystems, not local-filesystems, since
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.
I think the bug may be related to a recent change in portmap: indeed until recently portmap did start on "local- filesystems" , so /usr (and /var, etc.) was mounted before portmap starts, and statd starts after portmap, so statd could start properly.
portmap (6.0.0-1ubuntu2) lucid; urgency=low
* portmap should start on virtual- filesystems, not local-filesystems, since
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.