From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12821] filesystem corrupts on heavy I/O
Date: Fri, 6 Mar 2009 12:30:25 -0800 (PST) [thread overview]
Message-ID: <20090306203025.94793108042@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12821-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12821
------- Comment #12 from sandeen@redhat.com 2009-03-06 12:30 -------
Created an attachment (id=20449)
--> (http://bugzilla.kernel.org/attachment.cgi?id=20449&action=view)
stat of the problematic inode in (hacked) debugfs
This is for the ext4 devs as much as anything; it's a hacked stat <inode> of
the inode that generated the messages.
It does have 3 levels, which would be sufficient to enter the code that
generated the warning, due to what I believe is your bug.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-03-06 20:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 16:42 [Bug 12821] New: filesystem corrupts on heavy I/O bugme-daemon
2009-03-05 17:26 ` [Bug 12821] " bugme-daemon
2009-03-05 17:46 ` bugme-daemon
2009-03-05 18:06 ` bugme-daemon
2009-03-05 18:13 ` bugme-daemon
2009-03-05 18:59 ` bugme-daemon
2009-03-05 19:06 ` bugme-daemon
2009-03-05 19:25 ` bugme-daemon
2009-03-06 6:11 ` bugme-daemon
2009-03-06 7:16 ` bugme-daemon
2009-03-06 14:18 ` bugme-daemon
2009-03-06 20:21 ` bugme-daemon
2009-03-06 20:30 ` bugme-daemon [this message]
2009-03-10 10:03 ` bugme-daemon
2009-03-13 7:11 ` bugme-daemon
2009-03-13 15:03 ` bugme-daemon
2009-03-15 4:56 ` bugme-daemon
2009-03-15 5:23 ` bugme-daemon
2009-03-17 6:07 ` bugme-daemon
2009-03-17 6:07 ` bugme-daemon
2009-03-17 6:30 ` bugme-daemon
2009-03-17 15:28 ` bugme-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=20090306203025.94793108042@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--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).