The regression testing for e2fsck already involves running it a second time to make sure the file system is truly clean.
That is certainly something we strive for. If you get errors after running e2fsck -y (i.e., you say yes to fix all corruptions), then one of the following is true: (a) the hardware is buggy, (b) you ran e2fsck while the file system was mounted, or (c) there is a bug in e2fsck. Unfortunately I need a reproducible test case to be able be able do much more with this report. We already have regression tests that test blocks claimed by multiple files and where the blocks are cloned to fix this. -- 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
