Date: Mon, 4 Apr 2005 13:04:41 -0700
From: Andrew Morton <akpm@osdl.org>
To: cmm@us.ibm.com
Cc: andrea@suse.de, mjbligh@us.ibm.com, linux-kernel@vger.kernel.org,
       ext2-devel@lists.sourceforge.net, sct@redhat.com, janetinc@us.ibm.com
Subject: Re: OOM problems on 2.6.12-rc1 with many fsx tests
Message-Id: <20050404130441.53ab480b.akpm@osdl.org>
In-Reply-To: <1112633417.3703.8.camel@dyn318043bld.beaverton.ibm.com>
References: <20050315204413.GF20253@csail.mit.edu>
	<20050316003134.GY7699@opteron.random>
	<20050316040435.39533675.akpm@osdl.org>
	<20050316183701.GB21597@opteron.random>
	<1111607584.5786.55.camel@localhost.localdomain>
	<20050403183544.7c31f85c.akpm@osdl.org>
	<1112633417.3703.8.camel@dyn318043bld.beaverton.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1547
Lines: 37

Mingming Cao <cmm@us.ibm.com> wrote:
>
> On Sun, 2005-04-03 at 18:35 -0700, Andrew Morton wrote:
> > Mingming Cao <cmm@us.ibm.com> wrote:
> > >
> > > I run into OOM problem again on 2.6.12-rc1. I run some(20) fsx tests on
> > >  2.6.12-rc1 kernel(and 2.6.11-mm4) on ext3 filesystem, after about 10
> > >  hours the system hit OOM, and OOM keep killing processes one by one. I
> > >  could reproduce this problem very constantly on a 2 way PIII 700MHZ with
> > >  512MB RAM. Also the problem could be reproduced on running the same test
> > >  on reiser fs.
> > > 
> > >  The fsx command is:
> > > 
> > >  ./fsx -c 10 -n -r 4096 -w 4096 /mnt/test/foo1 &
> > 
> > 
> > This ext3 bug goes all the way back to 2.6.6.
> 
> > I don't know yet why you saw problems with reiser3 and I'm pretty sure I
> > saw problems with ext2.  More testing is needed there.
> > 
> 
> We (Janet and I) are chasing this bug as well. Janet is able to
> reproduce this bug on 2.6.9 but I can't. Glad to know you have nail down
> this issue on ext3. I am pretty sure I saw this on Reiser3 once, I will
> double check it.  Will try your patch today.

There's a second leak, with similar-looking symptoms.  At ~50
commits/second it has leaked ~10MB in 24 hours, so it's very slow - less
than a hundredth the rate of the first one.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/