From: Chris Mason <mason@suse.com>
To: Rob Shakir <rob@rshk.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/ext3/balloc.c:942!
Date: Thu, 06 May 2004 08:32:04 -0400 [thread overview]
Message-ID: <1083846724.11249.16.camel@watt.suse.com> (raw)
In-Reply-To: <20040505222408.GA10030@rshk.co.uk>
On Wed, 2004-05-05 at 18:24, Rob Shakir wrote:
> I've seen something vaguely similar to this problem, but rather than running
> ext3 I'm running ReiserFS.
>
> This problem has occured twice, but I've just got the machine back running to
> report the bug properly.
>
There was an additional error message from reiserfs before the bug,
could you please look for it in your logs?
Looks like you're on 2.6.5, the reiserfs logging fixes in 2.6.6-rc2 and
higher fix a few different ways you can oops in search_by_key.
-chris
next prev parent reply other threads:[~2004-05-06 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 21:31 kernel BUG at fs/ext3/balloc.c:942! Zwane Mwaikambo
2004-05-05 22:24 ` Rob Shakir
2004-05-06 12:32 ` Chris Mason [this message]
2004-05-06 17:00 ` Rob Shakir
2004-05-07 17:23 ` Mingming Cao
-- strict thread matches above, loose matches on Subject: below --
2004-08-03 23:15 Philip Molter
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=1083846724.11249.16.camel@watt.suse.com \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@rshk.co.uk \
/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