From: Sachin Sant <sachinp@in.ibm.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: jfs-discussion@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>,
shaggy@austin.ibm.com
Subject: Re: [Jfs-discussion] [BUG/JFS/2.6.29-rc8] kernel BUG at fs/mpage.c:473!
Date: Thu, 19 Mar 2009 12:03:26 +0530 [thread overview]
Message-ID: <49C1E736.1000508@in.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.01.0903180259110.16244@bogon.housecafe.de>
Christian Kujau wrote:
> On Mon, 16 Mar 2009, Sachin Sant wrote:
>
>> autorun: reading command 85 /usr/local/autobench/scripts/autobench.dat
>> autorun: run test fsstress -d $scratchdir -l $iterations: command read
>> autorun: run test fsstress -d /mnt/tmp -l 1: was expanded
>> 03/15/2009-19:36:37 processing command: (1) 'run test fsstress -d /mnt/tmp -l 1'
>>
>
> How many iterations were really run to hit this BUG? When I specify "-l
> 1", fsstress[0] comes back instantly (and no error of course)...
>
Sorry for the late reply. Somehow i missed this mail.
Yeah with default option values fsstress completes in a jiffy. I generally
invoke fsstress with 1000 operations per process (-n 1000) and 1000
processes (-p 1000).
fsstress -d /mnt/tmp -l 1 -n 1000 -p 1000
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-03-19 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 7:10 [BUG/JFS/2.6.29-rc8] kernel BUG at fs/mpage.c:473! Sachin Sant
2009-03-17 14:21 ` [Jfs-discussion] " Dave Kleikamp
2009-03-18 5:29 ` Sachin Sant
2009-03-18 10:05 ` Christian Kujau
2009-03-19 6:33 ` Sachin Sant [this message]
2009-03-20 1:50 ` Christian Kujau
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=49C1E736.1000508@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=shaggy@austin.ibm.com \
/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