On Sat, Jan 04, 2014 at 07:28:12AM -0000, Andrew Radke wrote: > In the past we have also been asked to update our kernels and at no > stage has this improved the situation. Is there anything to indicate > that it is likely to help on this occasion or that it is a kernel bug > and not a problem somewhere in the system startup scripts. It seems > quite possible that it is a bug where upstart believes that the network > is up when it's not.
If this is the case, it's necessarily a bug in either the kernel or the networking layer, not in upstart. Upstart itself (mountall) only tries to mount the network filesystems when it's received a notification that a network interface is up. It may not be the interface *needed* for the mount, but in this case it's expected to fail immediately and upstart will wait for the next network interface before retrying. If this is a kernel bug, it's an obscure one, and I don't see any point in having you retest with newer upstream kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1118447 Title: Race condition with network and NFS mounts causes boottime hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1118447/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
