From: Chris Mason <mason@suse.com>
To: David Wysochanski <davidw@netapp.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: reiserfs and SCSI oops seen in 2.6.9-rc2 with local SCSI disk IO
Date: Mon, 27 Sep 2004 16:44:59 -0400 [thread overview]
Message-ID: <1096317899.19249.40.camel@watt.suse.com> (raw)
In-Reply-To: <4154404B.3070705@netapp.com>
On Fri, 2004-09-24 at 11:42 -0400, David Wysochanski wrote:
> Matthew Wilcox wrote:
> > On Fri, Sep 24, 2004 at 11:03:08AM -0400, David Wysochanski wrote:
> > > I can reproduce this pretty easily with local disk.
> > >
> > > Here's some details about my setup (attached is the
> > > full kernel config):
> > > - dell 2650 (dual xeon, hyperthreading disabled)
> > > - 1 local SCSI disk (root volume)
> > > - 2 local SCSI disks (data), each with 10 partitions
> > > of 100MB each, 6 of them reiserfs filesystems, 3 of them
> > > ext3, and 3 of them ext2 (total of 20 unique filesystems)
> > > - one instance of test program running on each of the
> > > 20 filesystems
> >
Can you reproduce with a smaller test setup? Say just the 6 reiserfs
partitions of 100MB each? Is a mix of filesytems required to trigger
the bug or can you trigger with reiser alone?
I'm having a hard time triggering here, but since your oopsen so
consistently include roughly the same paths in reiserfs, I'd expect this
isn't a scsi problem. I've got an aic7892 card, so our test setups are
at least similar.
-chris
next prev parent reply other threads:[~2004-09-27 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 15:03 David Wysochanski
2004-09-24 15:18 ` Matthew Wilcox
2004-09-24 15:42 ` David Wysochanski
2004-09-24 17:58 ` Christoph Hellwig
2004-09-27 20:44 ` Chris Mason [this message]
2004-09-24 19:39 ` Barry K. Nathan
2004-09-24 19:42 ` David Wysochanski
2004-10-05 0:45 ` Chris Mason
2004-10-05 11:51 ` reiserfs and SCSI oops seen in 2.6.9-rc2 with local SCSI diskIO David Wysochanski
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=1096317899.19249.40.camel@watt.suse.com \
--to=mason@suse.com \
--cc=davidw@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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
Powered by JetHome