From: Ted Ts'o <tytso@mit.edu>
To: Matthias Erll <merll@web.de>
Cc: linux-ext4@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 42859] New: kernel BUG at fs/ext4/extents.c:1953
Date: Sun, 4 Mar 2012 20:51:21 -0500 [thread overview]
Message-ID: <20120305015121.GB9087@thunk.org> (raw)
In-Reply-To: <4F53E874.5050201@web.de>
On Sun, Mar 04, 2012 at 11:11:00PM +0100, Matthias Erll wrote:
>
> In the three cases I can reproduce, the inode number has been identical.
> Please find the debugfs output below.
Thanks, this is helpful. It is indeed a bug in e2fsck; it's not
noticing the case where the extent length is zero (but the extent
header was still valid). The workaround is to run the following
commands with the file system unmounted:
# debugfs -w -R "clri <1312385>" /dev/sda2
# e2fsck -f /dev/sda2
I'll get this fixed in the next maintenance release of e2fsprogs.
- Ted
next prev parent reply other threads:[~2012-03-05 1:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 14:39 [Bug 42859] New: kernel BUG at fs/ext4/extents.c:1953 bugzilla-daemon
2012-03-04 20:27 ` Ted Ts'o
2012-03-04 22:11 ` Matthias Erll
2012-03-05 1:51 ` Ted Ts'o [this message]
2012-04-04 14:59 ` [Bug 42859] " bugzilla-daemon
2012-06-13 15:14 ` bugzilla-daemon
2012-06-13 15:14 ` bugzilla-daemon
2020-03-11 12:17 ` bugzilla-daemon
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=20120305015121.GB9087@thunk.org \
--to=tytso@mit.edu \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=merll@web.de \
/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).