I've searched the lists and only saw a previous reference to possibly harmless 'make check' failures on this version, so I'll just ask. I've been trying to get ext4 running for some time, but it appears to be working normally lately. e4defrag and mballoc patches also appear to be working fine (everything against 2.6.22.1). But that version of e2fsprogs (1.39-tyt3), even with the last round of patches against it, appears to generate many bogus errors when checking the filesystem with 'fsck -fn'. While using 'data=journal' and other things should reduce the chance of needing a fsck, it makes me worried. Is there anything at current that can get around this all, or verify that the errors it's coming up with are indeed bogus (they certainly look it, hundreds of errors at block 0 or -1, for instance)? For previous attempts at ext4, running that version of e2fsprogs would come up with legitimate looking errors, then 'fix' it. But even rebooting immediately afterwards into emergency read-only mode would generate the same errors again. Multiple attempts to fix the errors (with probable legitimate corruption on a few files from a bad attempt at getting e4defrag working) effectively just shredded the filesystem. Ext4 is appearing rather stable right now, which is also making me think it's fsck's fault. - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
