linux-ext4 - Re: ext4_ext_check_inode: bad header/extent in inode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090424032028.GB7949@mit.edu>
Date:	Thu, 23 Apr 2009 23:20:28 -0400
From:	Theodore Tso <tytso@....edu>
To:	Christian Kujau <lists@...dbynature.de>
Cc:	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: ext4_ext_check_inode: bad header/extent in inode

On Thu, Apr 23, 2009 at 03:15:10PM -0700, Christian Kujau wrote:
> On Thu, 23 Apr 2009, Theodore Tso wrote:
> > Eventually I might need a raw e2image dump, i.e.:
> > 
> > 	   e2image -r /dev/md0 - | bzip2 > /var/tmp/md0.e2i.bz2
> 
> I've put the raw e2image dump on http://nerdbynature.de/bits/2.6.30-rc2/
> Do you still need the dump without the "-r"?

Nope, the raw e2image file was perfect.  This was actually a problem I
knew about, and wanted to get fixed before the e2fsprogs 1.41.5
release.  The problem was that i_file_acl_high was set and the kernel
unconditionally checks for it even though the INCOMPAT_64_BITS flag is
not set.

It's been fixed in e2fpsrogs 1.41.5, which I've only just released.
It's available on git, sourceforge, and all of the other usual places.
This should fix the problem for you.

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html