Public bug reported:
Binary package hint: e2fsprogs
Just happened to me, on up-to-date lucid, amd64 on ext4.
I had some corruption error on my hard drive, which were picked up by fsck on
reboot. fsck did its magic, then rebooted. On next reboot, the following
infinite loop occured: fsck gets invoked, says there are orphaned nodes in a
linked list, and says it can't fix it because it was invoked automatically
(with -a or -p). Then it dies, but init scripts run it again. It fails with the
same diagnostic, and so on. I couldn't bypass fsck by getting into recovery
mode, so I had to run fsck from a live USB. Obviously, I can't reproduce this
bug. Could it be that the init script forgets to check the return code? fsck
says 4 is OR'd into the return code whenever there is a problem it can't fix in
noninteractive mode.
** Affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
--
fsck complains some errors can't be fixed, then loops
https://bugs.launchpad.net/bugs/554349
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
