linux-ext4 - Re: Kernel 3.7.0: bad header/extent

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: <20121216022753.GD9016@thunk.org>
Date:	Sat, 15 Dec 2012 21:27:53 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Dâniel Fraga <fragabr@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Kernel 3.7.0: bad header/extent

On Sat, Dec 15, 2012 at 06:44:26PM -0200, Dâniel Fraga wrote:
> 	After upgrading from kernel 3.6.0 to 3.7.0 (x86-64) I got this:
> 
> Dec 15 18:38:28 tux kernel: EXT4-fs error (device sda2): 
> ext4_ext_check_inode:462: inode #9311628: comm less: bad header/extent:
> invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
> 
> 	So I tried to run e2fsck and it "fixed" inode 9311628. Running 
> e2fsck again doesn't detect any errors, but the problem remains.

What do you mean "the problem remains"?  Are you getting the same
EXT4-fs error message when you try to access the file?

Can you send the output of the command:

	debugfs -R "stat <9311628>"/dev/sda2

Thanks!!

						- 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