From: Andrew Morton <akpm@osdl.org>
To: "Maarten Maathuis" <madman2003@gmail.com>
Cc: shaggy@austin.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: 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: Fri, 4 Aug 2006 01:52:21 -0700 [thread overview]
Message-ID: <20060804015221.dbcfa9d6.akpm@osdl.org> (raw)
In-Reply-To: <6d4bc9fc0608040053x4d7a9e14xe9de793cd0787736@mail.gmail.com>
On Fri, 4 Aug 2006 09:53:14 +0200
"Maarten Maathuis" <madman2003@gmail.com> wrote:
> On 8/4/06, Dave Kleikamp <shaggy@austin.ibm.com> wrote:
> > On Thu, 2006-08-03 at 18:27 +0200, Maarten Maathuis wrote:
> > > 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.
Increasing /proc/sys/vm/vfs_cache_pressure should increase the inode/dentry
reclaim rate.
> >
> > echo 2 > /proc/sys/vm/drop_caches
> >
> > This feature is relatively new.
> >
>
> Thank you, i tried echo'ing a 1 into that and it had no effect iirc.
1 drops pagecache, 2 drops dentries and inodes. Pagecache pins inodes, so
using 2 will drop less inodes than using 3.
> Documentation on /proc/sys/vm seems pretty scarce.
Documentation/filesystems/proc.txt
next prev parent reply other threads:[~2006-08-04 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 16:27 heavy file i/o on ext3 filesystem leads to huge ext3_inode_cache and dentry_cache that doesn't return to normal for hours Maarten Maathuis
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 [this message]
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=20060804015221.dbcfa9d6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madman2003@gmail.com \
--cc=shaggy@austin.ibm.com \
/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