It may be far worse than that. If you have separate partitions, and apache needs /var/www to be mounted in order for it to function correctly, letting the boot process proceed before the other partitions are fsck'ed and rebooted will cause apache to fail. Trying to run fsck in parallel is a very, very dangerous thing to do in general, since you don't know what partitions might be needed by system daemons during the boot-up process. That's dependent on how the system administrator may have set up the system. So it's not enough just to wait for the root partition to be fsck'ed; *all* partitions must be checked before the rest of the init scripts are allowed to proceed.
If you want fast fsck times, please see http://thunk.org/tytso/blog/2008/08/08/fast-ext4-fsck-times Running fsck in parallel is not the answer. -- Parallel fsck leads to unhelpful error message at login https://bugs.launchpad.net/bugs/255562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
