| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.6.39-rc4+: oom-killer busy killing tasks |
| From: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
| Date: | Mon, 25 Apr 2011 02:50:12 -0700 (PDT) |
| Cc: | LKML <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <alpine.DEB.2.01.1104250053590.18728@xxxxxxxxxxxxxx> |
| References: | <alpine.DEB.2.01.1104211841510.18728@xxxxxxxxxxxxxx> <20110424234655.GC12436@dastard> <alpine.DEB.2.01.1104250053590.18728@xxxxxxxxxxxxxx> |
| User-agent: | Alpine 2.01 (DEB 1266 2009-07-14) |
On Mon, 25 Apr 2011 at 01:02, Christian Kujau wrote: > On Mon, 25 Apr 2011 at 09:46, Dave Chinner wrote: > > BTW, what are your mount options? If it is the problem I suspect it > > is, then using noatime with stop it from occurring.... > > When mounted with noatime, running du(1) accross the XFS volume still > triggered the OOM killer, but the backtrace looked somewhat different > this time: Tried again with noatime, this time no OOM message got logged to the disk (but may have been logged to the console early on). As it's reproducible, I started du(1) across the XFS volume and after a while my SSH connection to the box was lost. That's all I got this time: http://nerdbynature.de/bits/2.6.39-rc4/oom/oom-6.JPG http://nerdbynature.de/bits/2.6.39-rc4/oom/slabinfo-6.txt.bz2 Christian. -- BOFH excuse #272: Netscape has crashed |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.6.39-rc4+: oom-killer busy killing tasks, Christian Kujau |
|---|---|
| Next by Date: | Re: [patch] xfsprogs: fixes a regression hang in xfs_repair phase 4, Ajeet Yadav |
| Previous by Thread: | Re: 2.6.39-rc4+: oom-killer busy killing tasks, Christian Kujau |
| Next by Thread: | 2.6.39 delaylog default mount status, Stan Hoeppner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |