From: Robert Derr <rderr@weatherflow.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.13.3 Memory leak, names_cache
Date: Thu, 06 Oct 2005 14:34:25 -0400 [thread overview]
Message-ID: <43456E31.8000906@weatherflow.com> (raw)
Hello,
I'm having a problem with a memory leak in the kernel. I'm running
2.6.13.3 from kernel.org on FC4 on a Dell Poweredge 2850 Duel Xeon 3ghz
with 2GB RAM. Soon after booting up names_cache starts growing until it
consumes all available memory on the system until the oom killer goes
nuts and starts killing all the processes on the machine. After
googling the problem I thought it could be caused by a corrupt file
system but after running fsck the problem hasn't gone away. Here's the
entry from /proc/slabinfo:
names_cache 204686 204686 4096 1 1 : tunables 24 12
8 : slabdata 204686 204686 12
Anyone have an idea what could cause this problem or point me in the
correct direction?
Thanks,
Robert J Derr
Weatherflow, Inc.
next reply other threads:[~2005-10-06 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 18:34 Robert Derr [this message]
2005-10-06 19:03 ` 2.6.13.3 Memory leak, names_cache Linus Torvalds
2005-10-06 19:24 ` Robert Derr
2005-10-06 19:54 ` Linus Torvalds
2005-10-06 20:03 ` Rick Lindsley
2005-10-06 21:17 ` Robert Derr
2005-10-06 21:31 ` Linus Torvalds
2005-10-06 23:31 ` Al Viro
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=43456E31.8000906@weatherflow.com \
--to=rderr@weatherflow.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.