linux-ext4 - Re: linux ext filesystem errors

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

Message-ID: <20131020152437.GA21285@thunk.org>
Date:	Sun, 20 Oct 2013 11:24:37 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Markus Moeller <huaraz@...ller.plus.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: linux ext filesystem errors

It's not clear how or why e2fsck is getting killed, so it's hard to
say.  It could be bug in e2fsck; or it could be any number of things.
If you're willing to compile your own version of e2fsprogs, it would
be great to download the latest e2fsprogs git tree, use the maint
branch, and then build the latest version of e2fsck, which by default
will come with debugging enabled, and see if you can replicate the
failure using the latest version of e2fsck.  (1.42.6 is a bit old, so
it might not be applicable with the latest version; I also don't know
how your distro might have compiled e2fsprogs).

If you can still get it to fail, it would be good to run it under gdb
so we can see the stack trace when it got killed.  Also, if you can
grab a raw e2image dump while the file system is unmounted, that could
be useful for us to try to debug what is going on.

Regards,

						- 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