Thanks. This was certainly standalone (root fsck failed during bootup sequence), so either HW or SW bug. I will be swapping the server out in about a week, and will look at putting a second drive in so I can dd an image before fsck'ing. Then, assuming it's SW and not HW, I should be able to reproduce the behavior on demand. I'm happy to hear about your thorough regression testing! Please feel free to close this bug and I'll post something new if I can get a reproducible situation for your consideration.
Regards, Andy Valencia -- fsck.ext4 marks FS clean when still damaged https://bugs.launchpad.net/bugs/615899 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
