From: Sachin Sant <sachinp@in.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@sun.com>, linux-ext4@vger.kernel.org
Subject: Re: EXT4: kernel BUG at fs/jbd2/commit.c:533!
Date: Thu, 03 Sep 2009 09:31:03 +0530 [thread overview]
Message-ID: <4A9F3F7F.6030304@in.ibm.com> (raw)
In-Reply-To: <20090902223011.GA30497@mit.edu>
Theodore Tso wrote:
> On Wed, Sep 02, 2009 at 03:07:37PM -0600, Andreas Dilger wrote:
>
>> Given the nature of the test being run (fsstress) it seems entirely
>> possible that there is some transaction which doesn't reserve enough
>> credits for the operation in some rare corner case?
>>
>
> That's possible, although we're running fsstress in the XFSQA tests.
>
> Sanchin, what are the parameters used when you ran fsstress, and how
> big is the partition in question? How many CPU's are in the PowerPC
> system in question?
Hi Ted,
So i have not been able to recreate this again in my last attempt.
I will try couple of time to see if i can recreate this.
The box under test is a 4 way POWER6. The disk partition (/dev/sda4)
in question is about 19GB.
fsstress was invoked with -p 50 -n 1000 -c -f dwrite=0
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-09-03 4:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 11:18 EXT4: kernel BUG at fs/jbd2/commit.c:533! Sachin Sant
2009-09-02 12:09 ` Theodore Tso
2009-09-02 21:07 ` Andreas Dilger
2009-09-02 22:30 ` Theodore Tso
2009-09-03 4:01 ` Sachin Sant [this message]
2009-09-03 7:36 ` Sachin Sant
2009-09-04 5:00 ` Sachin Sant
2009-09-04 8:02 ` Aneesh Kumar K.V
2009-09-04 8:23 ` Sachin Sant
2009-09-08 14:21 ` Sachin Sant
2009-09-10 8:03 ` Aneesh Kumar K.V
2009-09-10 8:20 ` Sachin Sant
2009-09-18 9:07 ` Sachin Sant
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=4A9F3F7F.6030304@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).