Well, the problem is that we need to distinguish between a critical filesystem (like /usr) being not present, and something completely optional, like /media/disk. More of a concern is where a filesystem is critical for an application-level server, and if it's missing it causes the server to really go boom. So we could just do the "don't worry, be happy" approach and just silently ignore a missing filesystem, and then let the server come up skipping the filesystem check and the filesystem mount. But this could cause bigger problems and cause more troubles than if the server is left down.
I could see a system configuration option which has the "don't worry, be happy" philosophy, and the more careful mode. But that's an initscripts issue, not an e2fsprogs issue. Also, if the Ubuntu installer was automatically adding all of these entries to /etc/fstab, that might be a design flaw in the Ubuntu installer. -- Failed file system check, weird behaviour https://bugs.launchpad.net/bugs/68589 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
