Re: ext4_ext_check_inode: bad header/extent in inode

[Andreas Dilger <adilger@sun.com>]

On Apr 24, 2009  07:58 -0400, Theodore Ts'o wrote:
> It didn't; what had happened was that a garbage block had got written
> into the inode table.  This caused the kernel to complain about
> eh_magic being wrong in the inode table.  E2fsck 1.41.3 fixed those
> problems, but it ignored i_file_acl_high because the 64 bit feature
> flag was not set.  The kernel always pays attention to
> i_file_acl_high, regardless of whether the 64-bit feature flag is set
> or not.  Hence, the kernel was complaining and refused to touch those
> inodes.   
> 
> In any case, with e2fsck 1.41.5, I added code to fix i_file_acl_high
> getting set, and I was then able to mount the raw e2image file and not
> have any problems accessing the files in question, so I'm pretty sure
> that was the problem.

This sounds like another case for the "inode badness" patch that we've
developed, as it allows e2fsck to detect that the inode is just full of
garbage and clear the whole thing, instead of fixing it piecemeal and
leaving the sanitized garbage behind.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.