From: Andrew Morton <akpm@zip.com.au>
To: mb/ext3@dcs.qmul.ac.uk
Cc: linux-kernel@vger.kernel.org, ext3-users@redhat.com
Subject: Re: ext3 oops under moderate load
Date: Fri, 31 Aug 2001 19:41:08 -0700 [thread overview]
Message-ID: <3B904AC4.6A449086@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0108301740420.7921-100000@inconnu.isu.edu> <Pine.LNX.4.33.0108310759460.13139-100000@nick.dcs.qmul.ac.uk>
mb/ext3@dcs.qmul.ac.uk wrote:
>
> Hi bug hunters,
>
> I left my spangly new dual PIII with an ext3 partition on a Promise
> FastTrak 100TX2 being used both by a local process and knfsd for a few
> hours, and the following happened:
>
> [ 2.4.9-ac3 SMP (noapic) + the one patch from Zygo Blaxell to recognise
> the Promise card; now I have kupdated, kjournald and user-space processes
> trying to access the volume in question all in state 'D' ]
>
> kernel BUG at revoke.c:307!
Yours is the third report of this - it's definitely a bug in
ext3. I still need to work out how you managed to get a page
attached to the inode which has not had its buffers fed through
journal_dirty_data(). There seem to be several ways in which
this can happen.
Is it possible that you ran out of disk space on the relevant
partition shortly before it died?
-
next prev parent reply other threads:[~2001-09-01 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0108301740420.7921-100000@inconnu.isu.edu>
2001-08-31 7:19 ` ext3 oops under moderate load mb/ext3
2001-08-31 10:33 ` mb/ext3
2001-09-01 2:41 ` Andrew Morton [this message]
2001-09-01 6:29 ` mb/ext3
2001-09-03 21:14 ` Stephen C. Tweedie
2001-09-03 21:23 ` Stephen Tweedie
2001-09-03 23:10 ` Steve Kieu
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=3B904AC4.6A449086@zip.com.au \
--to=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb/ext3@dcs.qmul.ac.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.