Even if I upgrade to the latest upstream kernel I am disinclined to deliberately attempt to corrupt my file system to duplicate this. If you have any suggestions as to how I can test the issue on the new kernel without putting my data at risk I'm happy to do so but the only way I can think of is deliberately hard-resetting until something goes wrong, kind of like russian roulette.
This bug actually highlights two issues, first: ext4-fs crashing on mount, and second: shouldn't there be a way to boot and run fsck without the system mounting all the file systems first? Just found this bug marked expired which seems to be related to the second issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/560480 -- EXT4-fs crash on boot attempting to fix minor corruption https://bugs.launchpad.net/bugs/641741 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
