From: Jeff Blaine <jblaine@mitre.org>
To: linux-kernel@vger.kernel.org
Cc: jblaine@mitre.org
Subject: PROBLEM: oom-killer bringing machine down in 2.6.10
Date: Tue, 18 Jan 2005 13:13:30 -0500 [thread overview]
Message-ID: <41ED51CA.6010206@mitre.org> (raw)
I posted this to the NFS list and was told to post
here.
I have a box with 4GB. It's running Red Hat Fedora Core
3 with 2.6.10 as distributed by them. No custom kernel
compiling, and no desire :)
The problem reported below DID NOT happen with 2.4.21.
It did happen also with 2.6.9, and I cannot comment on
other kernels. So, it happens with 2.6.9 and 2.6.10,
but not 2.4.21, and anything else has not been tried.
I am trying to run Iozone with -g and an argument to it
that is larger than the physical memory in the NFSv3
client machine.
For instance, on this 4GB box, I am trying '-g 4224m'.
More specifically, the entire command line is:
./iozone -a -g 4224m -f /sol9box/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.
Reference: http://www.iozone.org/
reply other threads:[~2005-01-18 18:13 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=41ED51CA.6010206@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