From: Matthias Erll <merll@web.de>
To: Ted Ts'o <tytso@mit.edu>
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, 04 Mar 2012 23:11:00 +0100 [thread overview]
Message-ID: <4F53E874.5050201@web.de> (raw)
In-Reply-To: <20120304202708.GA9087@thunk.org>
Hi Ted,
Am 04.03.12 21:27, schrieb Ted Ts'o:
> On Sun, Mar 04, 2012 at 02:39:09PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
>> Messages "kernel BUG at fs/ext4/extents.c:1953" occur, which seem to be
>> triggered when running certain processes (reproducible with init and gdm). The
>> volume can be mounted without any apparent problems and e2fsck does not report
>> any errors. Nevertheless, the file system may have been corrupted during an
>> earlier system crash.
> Would you be willing to apply the following patch, and then see which
> inode number gets reported (and whether it is always the same inode
> number or one that varies) and then report back the results of running
> the following debugfs commands?
>
> (assuming the inode number is 12345)
>
> debugfs /dev/sdX
>
> debugfs: stat <12345>
> degbufs: ex <12345>
In the three cases I can reproduce, the inode number has been identical.
Please find the debugfs output below.
Kind regards,
Matthias
debugfs /dev/sda2
debugfs 1.42.1 (17-Feb-2012)
debugfs: stat <1312385>
Inode: 1312385 Type: regular Mode: 0664 Flags: 0x80000
Generation: 1339335381 Version: 0x00000000:00000001
User: 0 Group: 406 Size: 0
File ACL: 0 Directory ACL: 0
Links: 1 Blockcount: 0
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x4f53e0ab:3c51ed20 -- Sun Mar 4 22:37:47 2012
atime: 0x4eda803c:da6fb35c -- Sat Dec 3 21:02:04 2011
mtime: 0x4f53e0ab:3bd7da30 -- Sun Mar 4 22:37:47 2012
crtime: 0x4eda803c:da6fb35c -- Sat Dec 3 21:02:04 2011
Size of extra inode fields: 28
EXTENTS:
debugfs: ex <1312385>
Level Entries Logical Physical Length Flags
0/ 0 1/ 1 0 - 4294967295 5276276 - 4300243571 0
next prev parent reply other threads:[~2012-03-04 22:11 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 [this message]
2012-03-05 1:51 ` Ted Ts'o
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=4F53E874.5050201@web.de \
--to=merll@web.de \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.