public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: Klaus Dittrich <kladit@t-online.de>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>,
	gilbertd@treblig.org, nickpiggin@yahoo.com.au
Subject: dentry cache leak? Re: rsync out of memory 2.6.8-rc2
Date: Mon, 19 Jul 2004 13:20:47 +0200	[thread overview]
Message-ID: <20040719112047.GA14784@outpost.ds9a.nl> (raw)
In-Reply-To: <20040719091943.GA866@xeon2.local.here>

On Mon, Jul 19, 2004 at 11:19:43AM +0200, Klaus Dittrich wrote:

> I found out I could trigger the memory outage using du -s /disc1 too.

Including crashing and/or running out of swap? That would indicate that the
dentry cache is not cleaning itself up, or that something is wrong with
reference counting.

Can you run 'cat fs/dentry-state' before and after the du -s? (assuming
there is an 'after'. Also, which fs is /disc1 on? any messages in dmesg?

dentry-state
------------

Status of  the  directory  cache.  Since  directory  entries  are
dynamically allocated and deallocated, this file indicates the current
status. It holds six values, in which the last two are not used and are
always zero. The others are listed in table 2-1.


Table 2-1: Status files of the directory cache 
..............................................................................
 File       Content                                                            
 nr_dentry  Almost always zero                                                 
 nr_unused  Number of unused cache entries                                     
 age_limit  
            in seconds after the entry may be reclaimed, when memory is
short 
 want_pages internally                                                         


-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO

  reply	other threads:[~2004-07-19 11:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19  9:19 rsync out of memory 2.6.8-rc2 Klaus Dittrich
2004-07-19 11:20 ` bert hubert [this message]
     [not found]   ` <20040719113228.GA15295@outpost.ds9a.nl>
2004-07-19 12:56     ` dentry cache leak? " Klaus Dittrich
2004-07-26  1:06       ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2004-07-26 15:06 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
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
2004-08-01  9:47 Klaus Dittrich

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=20040719112047.GA14784@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --cc=gilbertd@treblig.org \
    --cc=kladit@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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