linux-ext4 - 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-next>] [day] [month] [year] [list]

Message-ID: <kainf9$btc$1@ger.gmane.org>
Date:	Sat, 15 Dec 2012 18:44:26 -0200
From:	Dâniel Fraga <fragabr@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: Kernel 3.7.0: bad header/extent

	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.

	The file I can't access is /usr/include/dlfcn.h (I was trying to compile openssh).

	Anyway, any hints how can I fix it?

	Thanks.

	Ps: if you need more information, just ask.

-- 
Linux 3.7.0: Terrified Chipmunk
http://www.youtube.com/DanielFragaBR
http://www.libertarios.org.br


--
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