From: Robert Hancock <hancockr@shaw.ca>
To: Nico Schottelius <nico-kernel-20071219@schottelius.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Out of memory and no killable processes: 2.6.22-2-686-bigmem
Date: Tue, 18 Dec 2007 18:43:22 -0600 [thread overview]
Message-ID: <4768692A.3030204@shaw.ca> (raw)
In-Reply-To: <fa.oSel00y9Hn5hvV3laxPiw9blEfU@ifi.uio.no>
Nico Schottelius wrote:
> Hello!
>
> We are running Debian with 2.6.22-2-686-bigmem on Dell Blade 1955 hardware
> and get a Kernel Panic with oom + message that there are no processes
> left to kill:
>
> http://home.schottelius.org/~nico/unix/linux/oom_no_killable-2.6.22-1.jpeg
>
> Anyone an idea, what's the cause for that? This error happened on two of
> those machines,
>
> What I can see in our analysis done with munin is that the number of
> open inodes and inode table size decreased within some days from 40k
> to next to zero. Munin uses
>
> awk '{print "used.value " $1-$2 "\nmax.value " $1}' < /proc/sys/fs/inode-nr
>
> to log those value (happened on both machines).
>
> Thanks for any hint and CC as usual, please.
How much RAM is in these machines? If you're running tons of memory, it
really is better to run a 64-bit kernel if possible. I believe there are
some cases where low memory can be pretty easily exhausted on machines
with lots of high memory.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-12-19 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.oSel00y9Hn5hvV3laxPiw9blEfU@ifi.uio.no>
2007-12-19 0:43 ` Robert Hancock [this message]
2007-12-19 5:55 ` Out of memory and no killable processes: 2.6.22-2-686-bigmem Nico Schottelius
2007-12-19 8:56 ` Parag Warudkar
2007-12-19 19:14 ` Jiri Slaby
2007-12-19 8:57 ` Jiri Slaby
2007-12-18 23:56 Nico Schottelius
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=4768692A.3030204@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-kernel-20071219@schottelius.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).