mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Quentin Godfroy <godfroy@clipper.ens.fr>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	David.Madore@ens.fr
Subject: Re: possible (ext4 related?) memory leak in kernel 2.6.26
Date: Tue, 30 Sep 2008 17:18:54 -0400	[thread overview]
Message-ID: <20080930211854.GZ10831@mit.edu> (raw)
In-Reply-To: <20080930202728.GA6358@goelette.ens.fr>

[ Reply-to set to linux-ext4@vger.kernel.org ]

On Tue, Sep 30, 2008 at 10:27:29PM +0200, Quentin Godfroy wrote:
> Hi lists,
> I'd like to report the following problem : after ~ 10 days' uptime on a
> Debian 2.6.26-1-686 kernel, my system becomes extremely sluggish and
> unresponsive and the OOM-killer starts targeting even innocent processes like
> identd or rsync (when the swap is disabled). The machine is low on RAM (192
> MB) but this has never been a problem before. As for the slowness, strace
> shows that the brk() syscall takes ages to complete; the blocking processes
> are in the D state (and for some reason the kernel gives no wchan info).
>
> Config has nothing unusual except that all fs are ext4, which I am begining
> to suspect may be the culprit, as every night some process stat()s and
> read()s something like 850,000 files, which is maybe fs-stressing; also,
> umounting then remounting /home makes the 'buffers' drop from 127304 to
> 55920 and partially solves the problem.
>
> Free reports a large and constantly growing 'buffers' figure (more than
> 50% of the available memory). No userland processes seems to be consuming
> lare amounts of memory (sum of RSS in 'ps aux' is about 30 megs), and the
> overall system is mostly idle.
> 
> for instance, the following command reports 
> 
> $ free ; dpkg -l '*' >/dev/null; dmesg | tail -n 2
>              total       used       free     shared    buffers     cached
> Mem:        190356     178920      11436          0     126104      12520
> -/+ buffers/cache:      40296     150060
> Swap:            0          0          0
> /* Waits a minute or so */
> Killed
> [811245.911859] Out of memory: kill process 6639 (dpkg-query) score 7292 or a child
> [811245.911972] Killed process 6639 (dpkg-query)
> 

Can you send the output of /proc/meminfo and /proc/slabinfo?

						- Ted

  reply	other threads:[~2008-09-30 21:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 20:27 Quentin Godfroy
2008-09-30 21:18 ` Theodore Tso [this message]
2008-09-30 22:23   ` Quentin
2008-10-03  0:35     ` Theodore Tso
2008-10-05  9:15       ` Quentin Godfroy
2008-10-05 12:27         ` Theodore Tso
2008-10-05 16:12           ` Quentin Godfroy
2008-10-06  2:50             ` Theodore Tso
2008-10-06 15:30               ` Eric Sandeen
2008-10-06 15:50                 ` Renato S. Yamane
2008-10-06 17:55                 ` Theodore Tso
2008-10-07 22:12                   ` Theodore Tso
2008-10-08  0:02                     ` Quentin Godfroy
2008-10-08  0:53                       ` Theodore Tso
2008-10-08 23:52                         ` Quentin Godfroy
2008-10-09  2:38                           ` Theodore Tso
2008-10-02 18:36 ` Aneesh Kumar K.V

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=20080930211854.GZ10831@mit.edu \
    --to=tytso@mit.edu \
    --cc=David.Madore@ens.fr \
    --cc=godfroy@clipper.ens.fr \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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

Powered by JetHome