linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Blaine <jblaine@mitre.org>
To: linux-kernel@vger.kernel.org
Subject: BUG: oom-killer active when overcommit_memory contains '2', and more...
Date: Thu, 20 Jan 2005 08:53:36 -0500	[thread overview]
Message-ID: <41EFB7E0.60701@mitre.org> (raw)

I see this as 2 bugs, personally, and will say right up front
that none of these problems exist in 2.4.10.  I don't mean
to sound flippant, but also have to say that the reality of
this is that I do not have the time to test things further
for anyone.  Filing this bug report is as much as I have time
for (in addition to all of the time I have spent on this
already before this message).

1.  Filling up the memory on a 2.6.10 box renders it completely
     and permanently useless even after the memory-filling process
     exits due to oom-killer's havoc.

     I came across this problem when running Iozone NFSv3
     benchmarks.  The client Linux box in question is running
     2.6.10 (Fedora Core 3 with latest updates) and has 4GB
     physical memory and 4GB in a swap partition.  To perform
     a proper Iozone benchmark for NFS testing, one needs to
     specify a test file size that is larger than the amount
     of memory in the client.  In my case, 4224MB is being
     specified:

          ./iozone -a -g 4224m -f /sol9server/testfile

     As soon as it finally gets to trying a file size of
     4194304, oom-killer steps in and starts blasting
     processes off my machine.  NFS stops functioning,
     RPC calls to the box fail, SSH connections are no
     longer accepted, and I generally have to hard
     powercycle the box.  That's pretty poor :)

2.  Andries Brouwer looked into this and asked me to try
     turning off oom-killer with the following command:

         echo 2 > /proc/sys/vm/overcommit_memory

     Re-running the 4GB benchmark with Iozone, this did
     nothing and oom-killer walked through the door blasting
     processes off of my machine, rendering it totally
     broken in the end.


                 reply	other threads:[~2005-01-20 13:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41EFB7E0.60701@mitre.org \
    --to=jblaine@mitre.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;
as well as URLs for NNTP newsgroup(s).