public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Miguel Figueiredo <elmig@debianpt.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.21 frozen for a few minutes, swapping to disk
Date: Tue, 01 May 2007 15:58:23 +1000	[thread overview]
Message-ID: <4636D6FF.9060707@yahoo.com.au> (raw)
In-Reply-To: <20070430224911.ac989f40.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Tue, 01 May 2007 15:42:30 +1000 Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> 
> 
>>>hm, a genuine oom on an all-ext3 data=ordered i386 system, just like a
>>>million other people.  How very weird.
>>>
>>>I assume all those pages on the LRU are pagecache pages which for some
>>>reason we're unable to reclaim.
>>
>>It looks like it used up all swap? I'd guess a memory leak in some
>>application, or maybe a page refcount leak somewhere.
> 
> 
> yes, I missed that.   The number of mapped pages is tiny so the thing has
> been trying to swap out like.

I didn't quite parse this :)

If the memory is leaking slowly, it could be eventually pushing
everything out to swap without having a large amount of mapped pages.

Or if something is slowly writing stuff to tmpfs, that may not show
up in mapped pages either.


> The question is: how much memory is free after the oom-killing storm?
> If it's "lots" then it's probably an application problem.  If it's
> "not much" then perhaps there's a kernel leak.

Yeah, or a tmpfs filesystem being filled up (what does `df` say?).

-- 
SUSE Labs, Novell Inc.

      reply	other threads:[~2007-05-01  5:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-29 10:28 2.6.21 frozen for a few minutes, swapping to disk Miguel Figueiredo
2007-04-30  7:30 ` Andrew Morton
2007-05-01  5:42   ` Nick Piggin
2007-05-01  5:49     ` Andrew Morton
2007-05-01  5:58       ` Nick Piggin [this message]

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=4636D6FF.9060707@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=elmig@debianpt.org \
    --cc=linux-kernel@vger.kernel.org \
    /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