From: Andrew Morton <akpm@zip.com.au>
To: Peter Rival <frival@zk3.dec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops on 2.5.15 with ext3 & AIM 7 shared workload
Date: Fri, 17 May 2002 12:52:03 -0700 [thread overview]
Message-ID: <3CE55F63.19F7D0E1@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.32.0205171451440.19851-100000@harley.zk3.dec.com>
Peter Rival wrote:
>
> I've recently built a 2x300MHz P2 system with 512MB of memory for a simple
> x86 testbed. To start with, I ran the AIM VII shared workload on the
> system, using the 18 SCSI disks that I have available with ext2
> filesystems. I got the following oops when I rebooted and started the run
> with ext3. This was only at the simulated '100 users' load point; the
> system is capable of ~1100 simulated users (i.e. the system was hardly
> heavily loaded). Does this look familiar to anyone, or is there
> somehting anyone needs me to do? Thanks!
>
> - Pete
>
> Assertion failure in journal_commit_transaction() at commit.c:523:
(When reporting ext3 problems, please specify the journalling
mode - it makes a rather large difference).
I'll assume it's data=ordered. If you're using data=journal
then please don't - it's not working very well in 2.5.15.
These patches:
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.15/ext3-no-steal.patch
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.15/sct-jbddirty.patch
Will likely fix it. Please let me know...
-
prev parent reply other threads:[~2002-05-17 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 18:59 Oops on 2.5.15 with ext3 & AIM 7 shared workload Peter Rival
2002-05-17 19:52 ` Andrew Morton [this message]
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=3CE55F63.19F7D0E1@zip.com.au \
--to=akpm@zip.com.au \
--cc=frival@zk3.dec.com \
--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 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.