From: Tobias Hennerich <Tobias@Hennerich.de>
To: Alexander Nyberg <alexn@dsv.su.se>
Cc: Timo Hennerich <Timo@Hennerich.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Vladimir Saveliev <vs@namesys.com>
Subject: Re: Strange memory leak in 2.6.x
Date: Thu, 17 Mar 2005 13:30:26 +0100 [thread overview]
Message-ID: <20050317133026.A4515@bart.hennerich.de> (raw)
In-Reply-To: <1110812292.2492.21.camel@localhost.localdomain>; from alexn@dsv.su.se on Mon, Mar 14, 2005 at 03:58:12PM +0100
Hello,
On Mon, Mar 14, 2005 at 03:58:12PM +0100, Alexander Nyberg wrote:
> > for one of the last results of /proc/page_owner. It seems to be
> > obvious that the memory-leak seems to be the first entry:
> >
> > $ less page_owner_sorted_20050314_0740.bz2
> > 881397 times:
> > Page allocated via order 0
> > [0xc013962b] find_or_create_page+91
> > [0xf8aa9955] reiserfs_prepare_file_region_for_write+613
> > [0xf8aaa606] reiserfs_file_write+1366
> > [0xc015765c] vfs_write+172
> > [0xc015776c] sys_write+60
> > [0xc0103879] sysenter_past_esp+82
>
> [resolved addresses => names]
> >
> > The sorted table of /proc/kallsyms looks like this:
> >
> > f8aa96f0 t reiserfs_prepare_file_region_for_write [reiserfs]
> > f8aaa0b0 t reiserfs_file_write [reiserfs]
> >
> > So I guess that we have a problem with the reiser filesystem??
> > We are using reiserfs 3.6...
>
> [added Vladimir Saveliev to CC]
>
> The only thing that stands out is big page cache. However, looking at
> the previous OOM output it shows that it is zone normal that is
> completely out of memory and that highmem zone has lots of free memory.
>
> Let's see if the big sharks know what is going on...
Hm, it seems like the big sharks are hunting other fishes at the moment...
I looked at the code myself - reiserfs_prepare_file_region_for_write
has more then 250 lines of code. I don't want to critize anyone, but
this function is a bit too long to be easily debugged.
Because we suspect the problem in reiserfs and we still have to reboot
the machine every other day, we will switch to ext3 now.
I will report if the problem disappears this way.
Best regards Tobias
--
T+T Hennerich GmbH --- Zettachring 12a --- 70567 Stuttgart
Fon:+49(711)720714-0 Fax:+49(711)720714-44 Vanity:+49(700)HENNERICH
UNIX - Linux - Java - C Entwicklung/Beratung/Betreuung/Schulung
http://www.hennerich.de/
next prev parent reply other threads:[~2005-03-17 12:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 12:37 Strange memory leak in 2.6.x Tobias Hennerich
[not found] ` <1110291647.2294.12.camel@boxen>
[not found] ` <20050308154042.A388@bart.hennerich.de>
2005-03-08 16:03 ` Alexander Nyberg
2005-03-09 1:38 ` Andrew Morton
2005-03-09 9:27 ` Tobias Hennerich
2005-03-11 17:32 ` Tobias Hennerich
2005-03-11 18:23 ` Alexander Nyberg
2005-03-12 12:32 ` Tobias Hennerich
2005-03-12 15:08 ` Alexander Nyberg
2005-03-12 18:08 ` Alexander Nyberg
2005-03-12 20:42 ` Tobias Hennerich
[not found] ` <1110661479.3360.11.camel@boxen>
2005-03-14 12:27 ` Timo Hennerich
2005-03-14 14:58 ` Alexander Nyberg
2005-03-17 12:30 ` Tobias Hennerich [this message]
2005-03-23 13:41 ` Alexander Nyberg
2005-03-23 16:57 ` Tobias Hennerich
2005-03-24 15:18 ` Alexander Nyberg
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=20050317133026.A4515@bart.hennerich.de \
--to=tobias@hennerich.de \
--cc=Timo@Hennerich.de \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=linux-kernel@vger.kernel.org \
--cc=vs@namesys.com \
/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