public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: Emmanuel Florac <eflorac@intellique.com>,
	xfs@oss.sgi.com, Nick Piggin <npiggin@suse.de>,
	opensuse-kernel@opensuse.org, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [opensuse-kernel] Re: 2.6.34-rc3: simple du (on a big xfs tree) triggers oom killer [bisected: 57817c68229984818fea9e614d6f95249c3fb098]
Date: Sat, 24 Apr 2010 15:41:50 -0700	[thread overview]
Message-ID: <4BD373AE.3000703@gmail.com> (raw)
In-Reply-To: <201004250030.40867.hpj@urpla.net>

On 04/24/2010 03:30 PM, Hans-Peter Jansen wrote:
> On Saturday 24 April 2010, 23:23:20 Emmanuel Florac wrote:
>> Le Sat, 24 Apr 2010 18:44:22 +0200 vous écriviez:
>>> Greg, you might search for a server using xfs filesystems and and a
>>> i586 kernel>= 2.6.33, (2.6.32.11 of SLE11-SP1 will serve as well),
>>> log in as an ordinary user, do a "du" on /usr, and wait for the other
>>> users screaming...
>>
>> I did precisely that, and didn't notice anything special (du on kernel
>> source tree) kernel 2.6.32.11, deadline scheduler, 7 drives RAID-6
>> array, 8GB RAM.
>
> I guess, you're not on this specific openSUSE git version of 2.6.32.11 (e.g.
> the preparation for SP1 of SLE11), which, as usual, carries a lot of stuff
> from later kernels. The offending patch was included in linux-2.6.33
> between -rc4 and -rc5:
>
> Committer
> Alex Elder<aelder@sgi.com>
> Author
> Dave Chinner<david@fromorbit.com>
> Author date
> 11.01.10 00:51
> Parent
> xfs: Avoid inodes in reclaim when flushing from inode cache
> Child
> xfs: Remove inode iolock held check during allocation
> Branch
> master origin (Merge branch 'for-linus' of git://git.kernel.org/pub/scm/...)
> Branch
> 2.6.33.1 (Linux 2.6.33)
> Follows
> v2.6.33-rc4 (Linux 2.6.33-rc4)
> Precedes
> v2.6.33-rc5 (Linux 2.6.33-rc5)
>
> Cheers,
> Pete

sh*t.. my bad just replied to the wrong
thread..

I'm tired.. please ignore this.

Justin P. Mattock

  parent reply	other threads:[~2010-04-24 22:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 22:49 2.6.34-rc3: simple du (on a big xfs tree) triggers oom killer Hans-Peter Jansen
2010-04-05  0:49 ` Dave Chinner
2010-04-05 11:35   ` Hans-Peter Jansen
2010-04-05 23:06     ` Dave Chinner
2010-04-06 14:52       ` 2.6.34-rc3: simple du (on a big xfs tree) triggers oom killer [bisected: 57817c68229984818fea9e614d6f95249c3fb098] Hans-Peter Jansen
2010-04-06 23:11         ` Dave Chinner
2010-04-07  1:45           ` Dave Chinner
2010-04-07 22:02             ` Hans-Peter Jansen
2010-04-12 22:32               ` Dave Chinner
2010-04-13  8:50                 ` Hans-Peter Jansen
2010-04-13  9:18                   ` Dave Chinner
2010-04-13  9:42                     ` Hans-Peter Jansen
2010-04-24 16:44                       ` Hans-Peter Jansen
2010-04-24 21:23                         ` Emmanuel Florac
2010-04-24 22:30                           ` Hans-Peter Jansen
2010-04-24 22:40                             ` [opensuse-kernel] " Justin P. Mattock
2010-04-24 22:41                             ` Justin P. Mattock [this message]
2010-04-25 13:04                             ` Emmanuel Florac
2010-04-25 16:27                         ` Greg KH
2010-04-25 16:57                           ` Christoph Hellwig
2010-04-25 18:18                             ` Greg KH
2010-04-26  0:36                           ` Dave Chinner
2010-04-27  0:02                             ` Greg KH
2010-04-26  0:32                         ` Dave Chinner

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=4BD373AE.3000703@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=eflorac@intellique.com \
    --cc=gregkh@suse.de \
    --cc=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=opensuse-kernel@opensuse.org \
    --cc=xfs@oss.sgi.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