From: kladit@t-online.de (Klaus Dittrich)
To: Klaus Dittrich <kladit@t-online.de>
Cc: Jan-Frode Myklebust <janfrode@parallab.uib.no>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: dentry cache leak? Re: rsync out of memory 2.6.8-rc2
Date: Tue, 27 Jul 2004 23:05:59 +0200 [thread overview]
Message-ID: <4106C3B7.10603@xeon2.local.here> (raw)
In-Reply-To: <4106BE6C.1030701@xeon2.local.here>
Klaus Dittrich wrote:
> Jan-Frode Myklebust wrote:
>
>> On Mon, Jul 26, 2004 at 11:39:34PM +0200, Klaus Dittrich wrote:
>>
>>
>>>>> cat /proc/sys/vm/vfs_cache_pressure shows 100.
>>>>>
>>>>
>>
>> What about trying to increase the vfs_cache_pressure which seemed
>> to solve what to me looks like a similar problem:
>>
>> http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&threadm=2m9Oo-Oo-17%40gated-at.bofh.it&rnum=1&prev=/groups%3Fhl%3Den%26ie%3DUTF-8%26safe%3Doff%26q%3Djan%2Bfrode%2Boom%2Bdsmc%26spell%3D1
>>
>>
>> http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&threadm=2mdfi-3cC-11%40gated-at.bofh.it&rnum=2&prev=/groups%3Fq%3Djanfrode%2Boom%2Bdsmc%26ie%3DUTF-8%26hl%3Den%26btnG%3DGoogle%2BSearch
>>
>>
>>
>> -jf
>>
>>
> I did a test with a value of 500. echo 500 >
> /proc/sys/vm/vfs_cache_pressure.
>
> The highest numbers a cat /proc/sys/fs/dentry-state then showed during
> a du -s were
> 780721 750505 45 0 0 0
>
> The system survied. No processes were killed.
>
> With vfs_cache_pressure=100 a cat /proc/sys/fs/dentry-state showed
> numbers of about 1090000 before processes got killed.
>
> Hope that helps to narrow the region to look for what has changed.
>
PS. Two concurrent du -s however "kernel: Out of Memory: Killed process .."
next prev parent reply other threads:[~2004-07-27 21:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 15:06 dentry cache leak? Re: rsync out of memory 2.6.8-rc2 Klaus Dittrich
2004-07-26 19:37 ` Andrew Morton
2004-07-26 20:02 ` Klaus Dittrich
2004-07-26 20:38 ` Andrew Morton
2004-07-26 21:39 ` Klaus Dittrich
2004-07-26 22:14 ` Jan-Frode Myklebust
2004-07-27 20:43 ` Klaus Dittrich
2004-07-27 21:05 ` Klaus Dittrich [this message]
2004-07-28 1:21 ` Nick Piggin
2004-07-28 15:06 ` Klaus Dittrich
2004-07-29 3:31 ` Nick Piggin
2004-07-29 21:07 ` Andrew Morton
2004-07-30 16:30 ` Marcelo Tosatti
2004-07-30 19:47 ` Andrew Morton
2004-07-31 2:01 ` Marcelo Tosatti
2004-07-31 17:23 ` Linus Torvalds
2004-07-31 21:39 ` Andrew Morton
2004-08-03 6:55 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2004-08-01 9:47 Klaus Dittrich
2004-07-19 9:19 Klaus Dittrich
2004-07-19 11:20 ` dentry cache leak? " bert hubert
[not found] ` <20040719113228.GA15295@outpost.ds9a.nl>
2004-07-19 12:56 ` Klaus Dittrich
2004-07-26 1:06 ` Andrew Morton
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=4106C3B7.10603@xeon2.local.here \
--to=kladit@t-online.de \
--cc=akpm@osdl.org \
--cc=janfrode@parallab.uib.no \
--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