[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A313F84.20900@sandeen.net>
Date: Thu, 11 Jun 2009 12:31:48 -0500
From: Eric Sandeen <sandeen@...deen.net>
To: Justin Piszcz <jpiszcz@...idpixels.com>
CC: linux-kernel@...r.kernel.org, xfs@....sgi.com
Subject: Re: Kernel 2.6.30: Memory/XFS leak, OOM killer kills many processes
Justin Piszcz wrote:
>
> On Thu, 11 Jun 2009, Justin Piszcz wrote:
>
>> Hello,
>>
>> I have a daily cron that backs up my root filesystem using xfsdump, it has
>> remain unchanged for at least 7-10 kernel versions. When I migrated to
>> 2.6.30, when the xfsdump ran at its scheduled time, nearly all of my
>> processes were killed due to an OOM situation, I can reproduce the situation.
>>
>> Kernel: 2.6.30
>> Dist: Debian Testing
>> xfsdump: 2.2.48-1
>
> Kernel 2.6.29.4 does not exhibit this problem:
>
> xfsdump: estimated dump size: 8694781376 bytes
> xfsdump: creating dump session media file 0 (media 0, file 0)
> xfsdump: dumping ino map
> xfsdump: dumping directories
> xfsdump: dumping non-directory files
> xfsdump: ending media file
> xfsdump: media file size 8294709848 bytes
> xfsdump: dump size (non-dir files) : 8208863560 bytes
> xfsdump: dump complete: 102 seconds elapsed
> xfsdump: Dump Status: SUCCESS
>
> XFS(?) bug in 2.6.30.
Any chance for a bisect run? :)
Or, just as a thought, watch slabtop while you run the dump?
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists