mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Maarten Maathuis" <madman2003@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: heavy file i/o on ext3 filesystem leads to huge ext3_inode_cache and dentry_cache that doesn't return to normal for hours
Date: Thu, 3 Aug 2006 18:27:04 +0200	[thread overview]
Message-ID: <6d4bc9fc0608030927t175f16c0kfef6a21cc521e368@mail.gmail.com> (raw)

I have a kernel specific problem and this seemed like a suitable place to ask.

I would like responces to be CC'ed to me if possible.

I use a 2.6.17-ck1 kernel on an amd64 system. I have observed this
problem on other/older kernels.

Whenever there is serious hard drive activity (such as doing "slocate
-u") ext3_inode_cache and dentry_cache grow to a combined 400-500 MiB.

The amount of objects is more than half a million.

This will slowly decrease to normal, but will take many hours. It does
not result in any OOM, because i have 1 GiB of memory.

As far as i understand hard drive cache should not be in the slab. Are
these just the inode's, because the amount of memory consumption seems
large for that?

I have found a way to clear the memory (and unfortunately most of the cache):

echo 100 > /proc/sys/vm/nr_hugepages
echo 0 > /proc/sys/vm/nr_hugepages

This suggest the kernel can free this memory. It's not the caching
that bothers me, what bothers me is that it seems to reside in the
slab.

I am not a developer, so please keep that in mind when replying.

I hope someone can be of help.

Sincerely,

Maarten Maathuis.

             reply	other threads:[~2006-08-03 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 16:27 Maarten Maathuis [this message]
2006-08-04  3:19 ` Dave Kleikamp
2006-08-04  3:27   ` Jeffrey V. Merkey
2006-08-04  7:53   ` Maarten Maathuis
2006-08-04  8:52     ` Andrew Morton
2006-08-04  9:43     ` 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=6d4bc9fc0608030927t175f16c0kfef6a21cc521e368@mail.gmail.com \
    --to=madman2003@gmail.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 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®