Re: ext4_ext_check_inode: bad header/extent in inode

[Eric Sandeen <sandeen@redhat.com>]

Theodore Tso wrote:
> On Fri, Apr 24, 2009 at 02:40:58AM -0700, Christian Kujau wrote:
>> Maybe the repair with 1.41.{3,4} before did something wrong and I should 
>> use 1.41.5 from the beginning? This issue is somewhat reproducible (given 
>> the fs holds enough files), so I could start over, corrupt the fs again 
>> and let e2fsprogs-1.41.5 do the whole job.
> 
> I doubt it; the problem was that the repair performed by e2fsck 1.41.3
> was simply imcomplete.  You can try to reproduce the corrupted
> filesystem again, but it should result in the same result.
> 
> Note that because there was garbage written into the inode table,
> there was going to be data loss; there's not much that can be done
> about that.  This just simple does a better job cleaning up after the
> mess, that's all.
> 
> 						- Ted
> 

But it's still got errors:

it fixed up inodes 12042, 12207, 12249 in lost+found plus "12090
(/t/#12090)" (?)

but post-mount:

sid:~# mount -t ext4 /dev/md0 /mnt/md0
sid:~# ls -la /mnt/md0/lost*
ls: cannot access /mnt/md0/lost+found/#12042: Input/output error
ls: cannot access /mnt/md0/lost+found/#12207: Input/output error
ls: cannot access /mnt/md0/lost+found/#12249: Input/output error
total 20
c????????? ? ?    ?        ?            ? #12042
s????????? ? ?    ?        ?            ? #12207
s????????? ? ?    ?        ?            ? #12249
drwx------ 2 root root 16384 Apr 23 21:16 .
drwxr-xr-x 5 root root  4096 Apr 23 21:15 ..

Christian, is there anything in dmesg along with it this time?

-Eric