From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>, cmm@us.ibm.com
Cc: andrea@suse.de, 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
Date: Mon, 04 Apr 2005 13:24:23 -0700 [thread overview]
Message-ID: <37420000.1112646263@flay> (raw)
In-Reply-To: <20050404130441.53ab480b.akpm@osdl.org>
>> > > 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.
What are you using to see these with, just kgdb, and a large cranial
capacity? Or is there some more magic?
m.
next prev parent reply other threads:[~2005-04-04 20:35 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
2005-03-26 0:20 ` [Ext2-devel] " 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 [this message]
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=37420000.1112646263@flay \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=janetinc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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 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.