I tested this with the following cases:
- clean fs, routine check, cancel
- clean fs, routine check, no cancel
- two clean fses with routine check, and mixed cancelling
- one ext3 and one reiserfsck
- corrupt ext3 root fs (I get to the console and get the fsck message, as well
as usable sulogin)
- corrupt ext3 non-root fs (dito about sulogin)
** Changed in: sysvinit (Ubuntu)
Status: In Progress => Fix Committed
--
fsck not repairing corruption on boot
https://bugs.launchpad.net/bugs/209416
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
