On Thu, Sep 12, 2013 at 08:17:12AM -0000, Stefan Bader wrote: > /mnt/cloud-images is nowait
Expected behavior; the mount point is outside of the "core" filesystem, so mountall does not block the boot waiting for it by default. You could mark the filesystem 'bootwait' in /etc/fstab, in which case mountall would tag it as 'remote' instead (... at least, that's what *should* happen!). > ... > local 4/4 remote 0/0 virtual 13/13 swap 1/1 > mounting event handled for /mnt/cloud-images > mounting /mnt/cloud-images > mount.nfs: Failed to resolve server nano: Name or service not known > mountall: mount /mnt/cloud-images [1451] terminated with status 32 > Filesystem could not be mounted: /mnt/cloud-images > mountall: Disconnected from Plymouth Also expected behavior (and I think there's at least one other open bug complaining about this). mountall knows that this is a network mount, but has no way to determine *which* network interface is required in order to reach it, so it will retry the mount after each network interface comes up... including lo. So yes, this results in a bit of noise in the logs. So all in all, I don't think there's anything here that explains the problem on the other machine, which is specific to having the NFS mount under /home. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223745 Title: Dependency resolver causes hang on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1223745/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
