On Mon, 2008-02-04 at 18:06 -0700, Andreas Dilger wrote: > Hmm, I wonder if e2fsck is calculating the wrong file offset or something? > The kernel appears to be taking the EA data offset from the end of > i_extra_isize and the ext3_xattr_ibody_header fields (so 0x88 + e_value_offs > from the start of the inode). > > Conversely, debugfs isn't having any problem with this EA at all. > > h, I think I see the problem, and this was fixed in newer e2fsck. > The EAs are stored "out of order" in the inode and older e2fsprogs > considered that an error. That was fixed in the final 1.40 release: > > Remove check in e2fsck which requires EA's in inodes to be sorted; > they don't need to be sorted, and e2fsck was previously wrongly > clearing unsorted EA's stored in the inode structure. Ah, I think you got it! I've just now reproduced the problem on one filesystem with the old e2fsck-1.40-WIP from Debian Etch and then checked again with the newer e2fsck-1.40.5 from Sid. The new version doesn't report any problems. Thanks very much for your time looking into this. Regards, Kevin. - 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
