> Hi, > > I am running 2.6.31-rc8+ and have ext4 corruption that will not go away. > > My root fs is ext4 on sdb3. I have moved the directory with corruption into lost+found and booted to a rescuse > system (arch linux) and run fsck.ext4 on the filesystem, which then reports its clean... Booting back into my > gentoo system and attempting to remove the xx directory from lost+found gives: > > [ 172.408799] EXT4-fs error (device sdb3): ext4_ext_check_inode: bad header/extent in inode #706801: invalid magic - magic 0, entries 0, max 0(0), depth 0(0) > [ 172.429410] EXT4-fs error (device sdb3): ext4_ext_check_inode: bad header/extent in inode #706801: invalid magic - magic 0, entries 0, max 0(0), depth 0(0) > [ 172.449920] EXT4-fs error (device sdb3): ext4_ext_check_inode: bad header/extent in inode #706801: invalid magic - magic 0, entries 0, max 0(0), depth 0(0) > > The above is repeatable. > > How can I _really_ clean this fs? What info is needed to help the process? > The first two pieces of information needed would be the version of e2fsprogs that you are running (e2fsck -V) and the stat of inode 706801: debugfs -R 'stat <706801>' /dev/sdb3 Thanks, Nick -- 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
