From: Jeff Garzik <jgarzik@pobox.com>
To: Brad Fitzpatrick <brad@danga.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] 2.6.9-rc4, dual Opteron, NUMA, 8GB
Date: Wed, 13 Oct 2004 16:50:46 -0400 [thread overview]
Message-ID: <20041013205046.GA792@havoc.gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0410131347590.31327@danga.com>
On Wed, Oct 13, 2004 at 01:49:08PM -0700, Brad Fitzpatrick wrote:
> On Wed, 13 Oct 2004, Jeff Garzik wrote:
>
> > Brad Fitzpatrick wrote:
> > > I was just about to mail and report that disabling NUMA does help:
> > >
> > > NUMA + mke2fs on LVM: OOPS (mailed earlier)
> > > no NUMA + mke2fs on LVM: okay
> > > NUMA + mke2fs on sdb1: OOPS (below)
> > > no NUMA + mke2fs on sdb1: okay
> > >
> > > no NUMA + mount e2fs on LVM: okay
> > > no NUMA + mount e2fs on sb1: okay
> > > NUMA + mount e2fs on LVM: okay
> > > NUMA + mount e2fs on sb1: untested, assume okay
> >
> >
> > Honestly it smells like a devmapper bug, with the pertinent test case
> > being some sort of behavior not normally generated by filesystem use
> > (the most common use case for block devices).
>
> Except for the data point above:
>
> NUMA + mke2fs on sdb1: OOPS (below)
>
> That's with devmapper totally out of the picture.
Ahh, indeed.
I think Andi did NUMA on x86-64?
Jeff
next prev parent reply other threads:[~2004-10-13 20:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 19:11 [OOPS] 2.6.9-rc4, dual Opteron, NUMA, 8GB Brad Fitzpatrick
2004-10-13 20:01 ` Jeff Garzik
2004-10-13 20:09 ` Brad Fitzpatrick
2004-10-13 20:12 ` Randy.Dunlap
2004-10-13 20:32 ` Brad Fitzpatrick
2004-10-13 20:34 ` Randy.Dunlap
2004-10-13 21:21 ` Andi Kleen
2004-10-14 6:07 ` Brad Fitzpatrick
2004-10-14 18:29 ` Brad Fitzpatrick
2004-10-14 18:40 ` Andi Kleen
2004-10-13 20:45 ` Jeff Garzik
2004-10-13 20:49 ` Brad Fitzpatrick
2004-10-13 20:50 ` Jeff Garzik [this message]
2004-10-13 20:38 ` Gnome-2.8 stoped working on kernel-2.6.9-rc4-mm1 Stef van der Made
2004-10-13 20:47 ` Radoslaw Szkodzinski
2004-10-13 21:16 ` Stef van der Made
2004-10-13 22:08 ` Buddy Lucas
2004-10-13 23:07 ` Jon Masters
2004-10-13 21:13 ` Jesse Stockall
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=20041013205046.GA792@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=brad@danga.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.