From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
aebr@win.tue.nl, cmm@us.ibm.com, andrea@suse.de,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: OOM problems on 2.6.12-rc1 with many fsx tests
Date: Wed, 23 Mar 2005 15:49:02 -0800 [thread overview]
Message-ID: <4242006E.4090408@us.ibm.com> (raw)
In-Reply-To: <20050323154232.376f977f.akpm@osdl.org>
Andrew Morton wrote:
> "Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
>>>>Nothing beats poking around in a dead machine's guts with kgdb though.
>>>
>>>Everyone his taste.
>>>
>>>But I was surprised by
>>>
>>>
>>>>SwapTotal: 1052216 kB
>>>>SwapFree: 1045984 kB
>>>
>>>Strange that processes are killed while lots of swap is available.
>>
>>I don't think we're that smart about it. If we're really low on mem, it
>>seems we invoke the OOM killer whether processes are causing the problem
>>or not.
>>
>>OTOH, if we can't free the kernel mem, we don't have much choice, but
>>it's not really helping much ;-)
>>
>
>
> I'm suspecting here that we simply leaked a refcount on every darn
> pagecache page in the machine. Note how mapped memory has shrunk down to
> less than a megabyte and everything which can be swapped out has been
> swapped out.
That makes sense. We have almost 485MB in active and inactive caches,
but we are not able reclai them :(
Active: 243580 kB
Inactive: 242248 kB
>
> If so, then oom-killing everything in the world is pretty inevitable.
>
next prev parent reply other threads:[~2005-03-23 23:51 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 ` Badari Pulavarty [this message]
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
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=4242006E.4090408@us.ibm.com \
--to=pbadari@us.ibm.com \
--cc=aebr@win.tue.nl \
--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=mbligh@aracnet.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.