From: Mark Wong <markw@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: ext3 journalling BUG on full filesystem
Date: Wed, 23 Mar 2005 12:21:30 -0800 [thread overview]
Message-ID: <20050323202130.GA30844@osdl.org> (raw)
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?
Mark
----- Forwarded message from Mark Wong <markw@osdl.org> -----
Date: Wed, 23 Mar 2005 08:05:30 -0800
To: linuxppc64-dev@ozlabs.org
From: Mark Wong <markw@osdl.org>
Subject: ext3 journalling BUG on full filesystem
Hi,
I'm running 2.6.11 and I'm suspecting that a full ext3 filesystem is
causing the following problem when performing some journaling
operation. Let me know if I can provide more details:
cpu 0x6: Vector: 700 (Program Check) at [c0000002e4f3f6d0]
pc: c0000000000a5fbc: .submit_bh+0x64/0x1fc
lr: c0000000000a62b4: .ll_rw_block+0x160/0x164
sp: c0000002e4f3f950
msr: 8000000000029032
current = 0xc00000038ff5c7c0
paca = 0xc000000000612000
pid = 1376, comm = kjournald
kernel BUG in submit_bh at fs/buffer.c:2706!
enter ? for help
6:mon> t
[c0000002e4f3f9f0] c0000000000a62b4 .ll_rw_block+0x160/0x164
[c0000002e4f3fab0] c000000000151ac4 .journal_commit_transaction+0xd88/0x16d4
[c0000002e4f3fe30] c000000000155590 .kjournald+0x114/0x308
[c0000002e4f3ff90] c000000000013ec0 .kernel_thread+0x4c/0x6c
next reply other threads:[~2005-03-23 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 20:21 Mark Wong [this message]
2005-03-23 22:00 ` ext3 journalling BUG on full filesystem Anton Blanchard
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=20050323202130.GA30844@osdl.org \
--to=markw@osdl.org \
--cc=linux-kernel@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