From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12885] kernel BUG at fs/jbd/transaction.c:1376!
Date: Wed, 18 Mar 2009 12:13:20 -0700 (PDT) [thread overview]
Message-ID: <20090318191320.6CD11108040@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12885-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12885
------- Comment #14 from tytso@mit.edu 2009-03-18 12:13 -------
In answer to your question in comment #12, yes, it's expected that processes
accessing the problematic directory might hang after a reboot, since when the
process died after the BUG, it probably left some locks locked, and so
processes would end up waiting forever for the locks to get unlocked (which
they won't since the process that held them died after the OOPS message).
But if this was caused by the unrar, then this might be harder to replicate....
In any case, if you haven't rebooted yet, I would try rebooting, and then
running e2fsck on the filesystem to make sure it is consistent. Then the next
trick is to see what is needed to replicate the BUG/oops message.
--
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-18 19:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 19:42 [Bug 12885] New: kernel BUG at fs/jbd/transaction.c:1376! bugme-daemon
2009-03-17 9:30 ` [Bug 12885] " bugme-daemon
2009-03-17 21:49 ` bugme-daemon
2009-03-18 14:46 ` bugme-daemon
2009-03-18 14:57 ` bugme-daemon
2009-03-18 14:58 ` bugme-daemon
2009-03-18 16:34 ` bugme-daemon
2009-03-18 17:41 ` bugme-daemon
2009-03-18 17:45 ` bugme-daemon
2009-03-18 17:51 ` bugme-daemon
2009-03-18 18:10 ` bugme-daemon
2009-03-18 18:14 ` bugme-daemon
2009-03-18 18:50 ` bugme-daemon
2009-03-18 19:11 ` bugme-daemon
2009-03-18 19:13 ` bugme-daemon [this message]
2009-03-18 21:12 ` bugme-daemon
2009-03-18 21:50 ` bugme-daemon
2009-03-18 22:04 ` bugme-daemon
2009-03-19 9:37 ` bugme-daemon
2009-03-19 21:41 ` bugme-daemon
2009-03-19 21:43 ` bugme-daemon
2009-03-19 21:51 ` bugme-daemon
2009-03-19 21:54 ` bugme-daemon
2009-03-20 7:23 ` bugme-daemon
2009-03-20 13:26 ` bugme-daemon
2009-03-21 7:12 ` 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=20090318191320.6CD11108040@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).