The badblocks program really isn't designed to catch maliciously designed "fake" flash FTL's. The "bit dropping pages" aren't necessarily constant, which means there might not be a set of block numbers that you can _put_ in the bad block inode. The bad block inode is a bad idea in these modern days anyway. It made sense back in the days of IDE disks, or its predecessors, which didn't do the bad block remapping in the drive firmware. These days, it just causes confusion and data loss by users who think it's a good idea.
I'm of half a mind of deprecating and disabling badblocks and e2fsck -cc in the next major release of e2fsprogs, since more and more users are using it to their detriment, and while I can't legislate away stupid user tricks, I can remove tools that invite stupid user tricks.... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/796717 Title: e2fsck not fixing some fs errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/796717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
