mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell Stuart <russell-lkml@stuart.id.au>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Problems with oom killer
Date: Wed, 12 Jul 2006 10:15:12 +1000	[thread overview]
Message-ID: <1152663312.4267.20.camel@ras.pc.brisbane.lube> (raw)

The oom killer is being run, and I can't figure out why.
As far as I can see there is plenty of memory available.
Attached are some logs that show that state of the machine
when the oom killer runs.

Background info: The machine has 2Gb of RAM, and 2Gb of
swap.  The oom killer consistently strikes when the
machine is doing a backup.  The backup consists of
mkfs'ing an ext3 partition, and then copying the files
across.  The oom killer does its stuff during the mkfs.
It goes away ones the next ext3 partition is mounted
and the backup starts.

It is running the Debian stable kernel (2.6.8.1) with
cfq on a dual core machine.  Although it shouldn't be,
it appears the machine is used a very high load at the
time because the shell script attached is supposed to
run every 5 seconds, yet at the time the oom condition
happens there is approx 10 minute delay between runs.

Two other odd things: there are many other machines
that are identical software wise, as in installed from 
the same DVD image, and doing an identical backup.  
This is the only one with the issue.  This box has
just been replaced and a fresh install done.  The 
previous box (completely different hardware) had the
same issue.

Any clues would be appreciated.

--

Regards,
Russell Stuart


             reply	other threads:[~2006-07-12  0:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  0:15 Russell Stuart [this message]
2006-07-12  0:23 ` Russell Stuart
2006-07-12 11:57 ` Alan Cox

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=1152663312.4267.20.camel@ras.pc.brisbane.lube \
    --to=russell-lkml@stuart.id.au \
    --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

all inboxes | Powered by JetHome®