[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20060804015221.dbcfa9d6.akpm@osdl.org>
Date: Fri, 4 Aug 2006 01:52:21 -0700
From: Andrew Morton <akpm@...l.org>
To: "Maarten Maathuis" <madman2003@...il.com>
Cc: shaggy@...tin.ibm.com, linux-kernel@...r.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
On Fri, 4 Aug 2006 09:53:14 +0200
"Maarten Maathuis" <madman2003@...il.com> wrote:
> On 8/4/06, Dave Kleikamp <shaggy@...tin.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists