From: Anton Blanchard <anton@samba.org>
To: Mark Wong <markw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 journalling BUG on full filesystem
Date: Thu, 24 Mar 2005 09:00:37 +1100 [thread overview]
Message-ID: <20050323220037.GR17561@krispykreme> (raw)
In-Reply-To: <20050323202130.GA30844@osdl.org>
Hi,
> I originally reported this to the linuxppc64-dev list, since I made it
> happen on a POWER system. I'm told this might be more generic...
>
> Anyone run into something like this?
Just in case it got lost in the rest of the xmon output... We hit a BUG():
kernel BUG in submit_bh at fs/buffer.c:2706!
Which looks like:
BUG_ON(!buffer_mapped(bh));
Backtrace:
ll_rw_block+0x160/0x164
journal_commit_transaction+0xd88/0x16d4
kjournald+0x114/0x308
kernel_thread+0x4c/0x6c
Anton
next prev parent reply other threads:[~2005-03-23 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 20:21 ext3 journalling BUG on full filesystem Mark Wong
2005-03-23 22:00 ` Anton Blanchard [this message]
2005-03-23 22:17 ` Darren Williams
2005-03-24 10:39 ` Jan Kara
2005-03-24 19:09 ` Stephen C. Tweedie
2005-03-24 19:38 ` Chris Wright
2005-03-24 21:24 ` Stephen C. Tweedie
2005-03-24 21:33 ` Chris Wright
2005-03-24 8:37 ` Jacky Malcles
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=20050323220037.GR17561@krispykreme \
--to=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markw@osdl.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