On Sun, Dec 16, 2012 at 01:00:25AM -0200, Dâniel Fraga wrote: > > Hi Ted! Yes, I get the same EXT4-fs message when I try to > access teh file. Here's the requested output: Um, really? **Exactly** the same error message? That doesn't make any sense. The error message you quoted happens when the kernel complains that the block numbers in the inode in question are invalid (i.e., are too big for the inode in question, or point at file system metadata). However, debugfs is not showing any extents --- which would be the case after e2fsck repaired the file system (it would have zapped the extent tree for the inode). So (a) you did run e2fsck on an unmounted file system right? (b) Can you send me the output of: debugfs -R "extents <9311628>" /dev/sda2 just to be sure we aren't missing anything. Also, if you are using a really new kernel such as 3.6.x or 3.7.x, you ***really*** shouldn't be using an ancient version of e2fsprogs such as 1.41.12. You really should be using e2fsprogs 1.42.x, preferably the latest e2fsprogs 1.42.6. I wonder if you are seeing a similar message indicating that the file system had previously found an error, and which wasn't cleared because you are using an ancient version of e2fsprogs.... - Ted -- 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
