On Wed, Aug 08, 2012 at 12:44:21PM -0000, Nikolaus Rath wrote: > Things aren't quite that simple. /home is an NFS mount transported over > VPN, and mountall generally dosn't mount it (presumably because the VPN > isn't up quickly enough).
Please show the /etc/fstab entry for this filesystem. The default behavior is that mountall will wait around until all network filesystems can be mounted, and it will retry mounting them each time it sees a network connection come up. And the 'filesystem' event is not emitted until all local and remote filesystems have been mounted - unless particular mount options have been specified that would cause that filesystem to be skipped. > It nevertheless happily emits the "filesystem" event. We tried solving > the problem by adding the explicit "mounted" event and starting a third > mountall run. So is the real problem here that mountall emits > "filesystem" even if it didn't mount all of them? Yes. It's possible this is a bug in mountall, but I suspect you may have a buggy mount option configured in /etc/fstab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Dependency loops due to ANDed start conditions leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
