From: Mingming Cao <cmm@us.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
andrea@suse.de, mjbligh@us.ibm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ext2-devel <ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] Re: OOM problems on 2.6.12-rc1 with many fsx tests
Date: Sun, 27 Mar 2005 11:22:32 -0800 [thread overview]
Message-ID: <1111951352.4313.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1111883038.3633.9.camel@dyn318043bld.beaverton.ibm.com>
On Sat, 2005-03-26 at 16:23 -0800, Mingming Cao wrote:
> On Fri, 2005-03-25 at 14:11 -0800, Badari Pulavarty wrote:
> > On Fri, 2005-03-25 at 13:56, 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 &
> > >
> > > I was able to reproduce this on ext3. Seven instances of the above leaked
> > > 10-15MB over 10 hours. All of it permanently stuck on the LRU.
> > >
> > > I'll continue to poke at it - see what kernel it started with, which
> > > filesystems it affects, whether it happens on UP&&!PREEMPT, etc. Not a
> > > quick process.
> >
> > I reproduced *similar* issue with 2.6.11. The reason I say similar, is
> > there is no OOM kill, but very low free memory and machine doesn't
> > respond at all. (I booted my machine with 256M memory and ran 20 copies
> > of fsx on ext3).
> >
> >
>
> Yes, I re-run the same test on 2.6.11 for 24 hours, like Badari see on
> his machine, my machine did not go to OOM on 2.6.11,still alive, but
> memory is very low(only 5M free). Killed all fsx and umount the ext3
> filesystem did not bring back much memory. I will going to rerun the
> tests without the mapped read/write to see what happen.
>
>
Run fsx tests without mapped IO on 2.6.11 seems fine. Here is
the /proc/meminfo after 18 hours run:
# cat /proc/meminfo
MemTotal: 510464 kB
MemFree: 6004 kB
Buffers: 179420 kB
Cached: 9144 kB
SwapCached: 0 kB
Active: 313236 kB
Inactive: 171380 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 510464 kB
LowFree: 6004 kB
SwapTotal: 1052216 kB
SwapFree: 1052216 kB
Dirty: 2100 kB
Writeback: 0 kB
Mapped: 24884 kB
Slab: 14788 kB
CommitLimit: 1307448 kB
Committed_AS: 78032 kB
PageTables: 720 kB
VmallocTotal: 516024 kB
VmallocUsed: 1672 kB
VmallocChunk: 514352 kB
elm3b92:~ # killall -9 fsx
elm3b92:~ # cat /proc/meminfo
MemTotal: 510464 kB
MemFree: 21332 kB
Buffers: 179668 kB
Cached: 8828 kB
SwapCached: 0 kB
Active: 298748 kB
Inactive: 171152 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 510464 kB
LowFree: 21332 kB
SwapTotal: 1052216 kB
SwapFree: 1052216 kB
Dirty: 1140 kB
Writeback: 0 kB
Mapped: 11648 kB
Slab: 14632 kB
CommitLimit: 1307448 kB
Committed_AS: 59800 kB
PageTables: 492 kB
VmallocTotal: 516024 kB
VmallocUsed: 1672 kB
VmallocChunk: 514352 kB
elm3b92:~ # umount /mnt/ext3
elm3b92:~ # cat /proc/meminfo
MemTotal: 510464 kB
MemFree: 181636 kB
Buffers: 22092 kB
Cached: 6740 kB
SwapCached: 0 kB
Active: 151284 kB
Inactive: 158948 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 510464 kB
LowFree: 181636 kB
SwapTotal: 1052216 kB
SwapFree: 1052216 kB
Dirty: 0 kB
Writeback: 0 kB
Mapped: 11656 kB
Slab: 14052 kB
CommitLimit: 1307448 kB
Committed_AS: 59800 kB
PageTables: 492 kB
VmallocTotal: 516024 kB
VmallocUsed: 1672 kB
VmallocChunk: 514352 kB
next prev parent reply other threads:[~2005-03-27 19:26 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 [this message]
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
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=1111951352.4313.4.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjbligh@us.ibm.com \
--cc=pbadari@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