Unfortunately I'm not going to be able to test as requested in the short
term as the systems involved are in production. I will see if I can
replicate it on some virtual machines but again it could be a while
until this is possible.
While I also understand the preference for up to date BIOS it should be
used with care for removing a confirmed bug status when it can be seen
that one person is out of date. We have multiple people reporting the
problem and it should not be assumed that no-one has up to date BIOS.
Please also don't take the following as me trying to be rude, it is
merely meant to be an observation of the history of the bug:
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.
I'm not an upstart expert so my observations here may be way off.
/etc/init/mountall-net.conf is set to start on net-device-up
/etc/init/network-interface.conf emits net-device-up but doesn't necessarily
configure anything other than the loopback interface
/etc/init/networking.conf also emits net-device-up
a "grep network /var/log/boot.log" on my system (that uses the noauto option
and mounts via /etc/rc.local) shows the following:
* Starting configure network device used by iSCSI root
[ OK ]
* Starting configure network device security
[ OK ]
* Starting configure network device security
[ OK ]
* Starting Mount network filesystems
[ OK ]
* Stopping Mount network filesystems
[ OK ]
* Starting configure network device
[ OK ]
* Starting Mount network filesystems
[ OK ]
* Stopping Mount network filesystems
[ OK ]
* Starting configure network device
[ OK ]
* Starting configure network device security
[ OK ]
* Starting configure virtual network devices
[ OK ]
* Stopping configure virtual network devices
[ OK ]
* Starting Serial port to network proxy ser2net
[ OK ]
Why is it that mountall-net (Mount network filesystems) is happening before
either network-interface (configure network device) or networking (configure
virtual network devices)?
And what would be the implications of removing "emits net-device-up" from
/etc/init/network-interface.conf so that we only get net-device-up once ifup -a
has been run rather than just a network interface is up?
--
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
