From: Andrew Morton <akpm@zip.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Christian Borntraeger <CBORNTRA@de.ibm.com>,
ext3-users@redhat.com, linux-kernel@vger.kernel.org,
Carsten Otte <COTTE@de.ibm.com>
Subject: Re: BUG: Assertion failure with ext3-0.95 for 2.4.7
Date: Fri, 10 Aug 2001 11:09:35 -0700 [thread overview]
Message-ID: <3B74235F.8F6943D9@zip.com.au> (raw)
In-Reply-To: <OF5E574EE5.AF3B6F6F-ONC1256AA2.0026D8D3@de.ibm.com> <3B72DD66.A6F65247@zip.com.au>, <3B72DD66.A6F65247@zip.com.au> <20010810104450.F31136@cpe-24-221-152-185.az.sprintbbd.net>
Tom Rini wrote:
>
> With this patch my first oops seems to have gone away. I'm repeating
> the test again, but dbench'ing 2,4,8,16,32 and then 64 (until disk
> space ran out) worked this time.
Thanks, Tom and Christian.
Yup, it's definitely a bug and the fix will be in 0.9.6 (in fact the way
things are looking at present it'll be the only substantive change in
0.9.6).
If it's possible, could you please also test journalled data mode?
It'd be interesting to sanity test recovery as well, but doing
thorough testing of recovery is hard. That's why the ext3 patch
places interesting debug/devel code way down inside the IDE device
driver...
next prev parent reply other threads:[~2001-08-10 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 8:46 BUG: Assertion failure with ext3-0.95 for 2.4.7 Christian Borntraeger
2001-08-08 9:26 ` Arjan van de Ven
2001-08-08 15:16 ` Tom Rini
2001-08-09 18:58 ` Andrew Morton
2001-08-10 17:44 ` Tom Rini
2001-08-10 18:09 ` Andrew Morton [this message]
2001-08-10 18:10 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2001-08-08 9:36 Christian Borntraeger
2001-08-08 14:38 Christian Borntraeger
2001-08-08 15:27 ` Tom Rini
2001-08-09 9:26 Christian Borntraeger
2001-08-13 6:53 Christian Borntraeger
2001-08-14 8:34 Christian Borntraeger
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=3B74235F.8F6943D9@zip.com.au \
--to=akpm@zip.com.au \
--cc=CBORNTRA@de.ibm.com \
--cc=COTTE@de.ibm.com \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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