public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Andrea Arcangeli <andrea@suse.de>,
	mjbligh@us.ibm.com, linux-kernel@vger.kernel.org,
	ext2-devel <ext2-devel@lists.sourceforge.net>
Subject: Re: OOM problems on 2.6.12-rc1 with many fsx tests
Date: Fri, 25 Mar 2005 19:17:02 -0500	[thread overview]
Message-ID: <20050326001702.GA22347@redhat.com> (raw)
In-Reply-To: <1111607584.5786.55.camel@localhost.localdomain>

On Wed, Mar 23, 2005 at 11:53:04AM -0800, Mingming Cao wrote:

 > The fsx command is:
 > 
 > ./fsx -c 10 -n -r 4096 -w 4096 /mnt/test/foo1 &
 > 
 > I also see fsx tests start to generating report about read bad data
 > about the tests have run for about 9 hours(one hour before of the OOM
 > happen). 

Is writing to the same testfile from multiple fsx's supposed to work?
It sounds like a surefire way to break the consistency checking that it does.
I'm surprised it lasts 9hrs before it breaks.

In the past I've done tests like..

for i in `seq 1 100`
do
  fsx foo$i &
done

to make each process use a different test file.

		Dave


  parent reply	other threads:[~2005-03-26  0:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 20:44 OOM problems with 2.6.11-rc4 Noah Meyerhans
2005-03-15 21:56 ` Sean
2005-03-15 22:12   ` Lee Revell
2005-03-15 23:46 ` Andrew Morton
2005-03-18 16:12   ` Noah Meyerhans
2005-04-13 13:47     ` Andrea Arcangeli
2005-04-14 16:56       ` Noah Meyerhans
2005-03-16  0:31 ` Andrea Arcangeli
2005-03-16 11:12   ` Andrea Arcangeli
2005-03-16 12:04   ` Andrew Morton
2005-03-16 12:15     ` Andrew Morton
2005-03-16 18:37     ` Andrea Arcangeli
2005-03-16 22:21       ` Andrew Morton
2005-03-23 19:53       ` OOM problems on 2.6.12-rc1 with many fsx tests Mingming Cao
2005-03-23 22:49         ` Andrew Morton
2005-03-23 23:13           ` Martin J. Bligh
2005-03-23 23:20             ` Andrew Morton
2005-03-23 23:26               ` Andries Brouwer
2005-03-23 23:30                 ` Martin J. Bligh
2005-03-23 23:42                   ` Andrew Morton
2005-03-23 23:49                     ` [Ext2-devel] " Badari Pulavarty
2005-03-24  1:49                     ` Andrea Arcangeli
2005-03-24  2:00                       ` Andrew Morton
2005-03-25 21:56         ` Andrew Morton
2005-03-25 22:11           ` [Ext2-devel] " Badari Pulavarty
2005-03-27  0:23             ` Mingming Cao
2005-03-27 19:22               ` Mingming Cao
2005-03-27 20:06                 ` Badari Pulavarty
2005-03-27 20:17                   ` Badari Pulavarty
2005-03-26  0:17         ` Dave Jones [this message]
2005-03-26  0:20           ` Badari Pulavarty
2005-04-04  1:35         ` Andrew Morton
2005-04-04 16:50           ` Mingming Cao
2005-04-04 20:04             ` Andrew Morton
2005-04-04 20:24               ` Martin J. Bligh
2005-04-04 20:33                 ` Andrew Morton
2005-04-05 17:04               ` [Ext2-devel] " Mingming Cao
2005-04-06  1:23                 ` Andrew Morton
2005-04-12 12:50                   ` Stephen C. Tweedie
2005-04-05 16:44           ` Stephen C. Tweedie
2005-03-16 12:23   ` OOM problems with 2.6.11-rc4 Andrew Morton
2005-03-16 12:30   ` Andrew Morton

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=20050326001702.GA22347@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=cmm@us.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjbligh@us.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