From: Theodore Ts'o <tytso@mit.edu>
To: Markus Moeller <huaraz@moeller.plus.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: linux ext filesystem errors
Date: Sun, 20 Oct 2013 11:24:37 -0400 [thread overview]
Message-ID: <20131020152437.GA21285@thunk.org> (raw)
In-Reply-To: <l40job$n86$1@ger.gmane.org>
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
prev parent reply other threads:[~2013-10-20 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 12:53 linux ext filesystem errors Markus Moeller
2013-10-20 14:47 ` Markus Moeller
2013-10-20 15:24 ` Theodore Ts'o [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131020152437.GA21285@thunk.org \
--to=tytso@mit.edu \
--cc=huaraz@moeller.plus.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).