To summarize, when booting a system, we have 2 options: - We use "bootwait" on all local filesystems (default) - We use "nobootwait" on all local filesystems.
The problem with "bootwait" is that it outright prevents the use of Ubuntu on a headless system. The problem with "nobootwait" is that is breaks possible dependencies between server applications and the underlying filesystem. Also there is the problem of being blind to what’s going on. You can tell there is an "fsck –a" running, that’s it. If it fails you only get a message in /var/log/boot.log. In short, assuming we don’t have a luxury of sitting in front of the server every time it boots, we need a slightly smarter "nobootwait" option. Fix1, If the system is running a background FSCK we NEED to be able to see what’s going on. For both the guy sitting on console and the admin connected via SSH. For this the best solution if to run FSCK in a screen session on TTY13+ Fix2, We need to let server applications KNOW to WAIT for the right filesystem to come online before they start. In upstart you can put a line like this: "start on mounted MOUNTPOINT=/home" Fix3, We the admins, NEED to know if a filesystem has not come online. A quick email to let us know. All 3 fixes are in place in the small sample script available here: https://bugs.launchpad.net/bugs/609864 Hope this helps, Gérald -- Boot hangs and unable to continue when automount disk in fstab is not available (Off or Disconnected) https://bugs.launchpad.net/bugs/571444 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
