From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
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: Fri, 3 Oct 2008 00:06:13 +0530 [thread overview]
Message-ID: <20081002183613.GC29613@skywalker> (raw)
In-Reply-To: <20080930202728.GA6358@goelette.ens.fr>
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).
>
> 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.
>
We actually fixed one in 6be2ded1d7c51b39144b9f07d2c839e1bd8707f1.
It is not really a memory leak. But yes it was not releasing some
the prealloc space memory.
-aneesh
prev parent reply other threads:[~2008-10-02 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 20:27 possible (ext4 related?) memory leak in kernel 2.6.26 Quentin Godfroy
2008-09-30 21:18 ` Theodore Tso
2008-10-02 18:36 ` Aneesh Kumar K.V [this message]
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=20081002183613.GC29613@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=David.Madore@ens.fr \
--cc=godfroy@clipper.ens.fr \
--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;
as well as URLs for NNTP newsgroup(s).