Comment 3 for bug 1157171

Revision history for this message
Steve Langasek (vorlon) wrote :

> And no mounting logs.

Is the /etc/init/statd-mounting.conf file present on your system? This job should trigger whenever mountall asks to mount an nfs filesystem, and block the mounting of that filesystem until statd has started. If the job file is missing, that would explain the behavior seen here.

If the job file were present, I would expect to see at least a /var/log/upstart/statd-mounting.log containing the line 'Terminated'. Are there some nfs mounts that *do* mount correctly at boot? (i.e., is the list of mounts complaining about missing statd complete, or does one of the nfs mounts actually mount successfully?) If the latter, this may be related to the following change that was made to nfs-common 1:1.2.6-3ubuntu2 in Ubuntu 12.10:

  * Add an instance to statd-mounting, and change it to just wait for statd
    instead of trying to trigger it potentially out of order. This also means
    we don't need to try to force portmap to start from statd.

You could try installing the nfs-common package from 12.10 to see if it addresses the problem for you. If it does, we could look at updating nfs-common in 12.04 with these fixes.

> Note that I have put _netdev in the fstab line, which should
> make mount wait until the network is available.

_netdev is a no-op for network filesystems.