xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16

from [Pavel Machek] [Permanent Link][Original]
To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
From: Pavel Machek <pavel@xxxxxx>
Date: Mon, 22 Jan 2007 13:37:35 +0000
Cc: linux-kernel@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.64.0701211424170.2552@p34.internal.lan>
References: <Pine.LNX.4.64.0701211424170.2552@p34.internal.lan>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.9i 
On Sun 2007-01-21 14:27:34, Justin Piszcz wrote:
> Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to invoke 
> the OOM killer and kill all of my processes?
> 
> Doing this on a single disk 2.6.19.2 is OK, no issues.  However, this 
> happens every time!
> 
> Anything to try?  Any other output needed?  Can someone shed some light on 
> this situation?

Is it highmem-related? Can you try it with mem=256M?

                                                        Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) 
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  TAKE 960195 - Patch for attr and acl to correctly use libtool while crosscompiling, Barry Naujok
Next by Date:  Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5), Justin Piszcz
Previous by Thread:  Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2, Justin Piszcz
Next by Thread:  Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2, Justin Piszcz
Indexes:  [Date] [Thread] [Top] [All Lists]