mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.18-rc6] ext3 memory leak
Date: Thu, 07 Sep 2006 07:31:19 -0400	[thread overview]
Message-ID: <200609070731.19124.gene.heskett@verizon.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0609071300330.1700@pcgl.dsa-ac.de>

On Thursday 07 September 2006 07:10, Guennadi Liakhovetski wrote:
>Hi all,
>
>this looks like a serious problem to be fixed before 2.6.18 final and
>backported to 2.6.17.*. Or a case of me misunderstanding something, in
>which case, please, let me know.
>
>I've reported before in thread "[2.6.17.4] slabinfo.buffer_head
> increases" a memory leak in ext3. Today I verified it is still present
> in 2.6.18-rc6.
>
>A short description: as long as write accesses are made on an ext3
>filesystem /proc/slabinfo buffer_head increases unboundedly. This
>behaviour is not observed with another journalling filesystems (e.g.,
>reiserfs), or if ext3 is mounted as ext2.
>
What would you call the 'get excited' level?  Here, with about 12 hours of 
uptime (I had an unlogged machine shutdown while I was offsite yesterday), 
I'm showing 

buffer_head        67158  67158     48   78    1 : tunables  120   60    
0 : slabdata    861    861      0

There are other entries that are larger here.  However I do note that its 
growing on a per cycle basis as fetchmail is doing its thing every 90 
seconds.  Now its
buffer_head        67672  67704     48   78    1 : tunables  120   60    
0 : slabdata    868    868      0

So perhaps thats why it did the shutdown?  With absolutely zip in the logs?

Although, my firewall box was also reset/rebooted about the same time as 
this ones powerdown according to an uptime report on it just now, so my 
ups must not be doing its thing correctly.

>As it seems serious enough to me I'm sending it to ext3 maintainers.
>
>Thanks
>Guennadi
>---------------------------------
>Guennadi Liakhovetski, Ph.D.
>DSA Daten- und Systemtechnik GmbH
>Pascalstr. 28
>D-52076 Aachen
>Germany
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

  reply	other threads:[~2006-09-07 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 11:10 Guennadi Liakhovetski
2006-09-07 11:31 ` Gene Heskett [this message]
2006-09-07 15:21 ` Guennadi Liakhovetski
2006-09-07 16:21   ` Gene Heskett
2006-09-07 16:34   ` Andrew Morton
2006-09-08  7:38     ` Guennadi Liakhovetski

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=200609070731.19124.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --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®