linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Wysochanski <davidw@netapp.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: 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: Fri, 24 Sep 2004 11:42:03 -0400	[thread overview]
Message-ID: <4154404B.3070705@netapp.com> (raw)
In-Reply-To: <20040924151828.GC16153@parcelfarce.linux.theplanet.co.uk>

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
> 
> I don't think this is a SCSI problem.  Your backtrace doesn't include
> anything in the SCSI subsystem (this doesn't _prove_ anything, but does
> suggest you should look elsewhere first).  You also didn't mention what
> SCSI controller you were using.  If you can reproduce the oops without
> using reiserfs at all, that would suggest the problem doesn't lie in
> reiserfs, but that's where I'd blame first ;-)
> 

I've been seeing a lot of problems with reiserfs that I
don't see on ext2 or ext3, so I would tend to agree with you.
Do you know where I could post for the reiserfs folks?

Did you see the backtrace for the second CPU?  It does
include SCSI and block subsystem components.


The controller on board the dell 2650 is Adaptec:

0000:02:06.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 01)
         Subsystem: Adaptec AHA-3960D U160/m
         Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 24
         BIST result: 00
         I/O ports at cc00 [disabled] [size=fcc00000]
         Memory at fcd01000 (64-bit, non-prefetchable) [size=4K]
         Expansion ROM at 00020000 [disabled]
         Capabilities: <available only to root>

0000:02:06.1 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 01)
         Subsystem: Adaptec AHA-3960D U160/m
         Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 25
         BIST result: 00
         I/O ports at c800 [disabled] [size=fcc00000]
         Memory at fcd00000 (64-bit, non-prefetchable) [size=4K]
         Expansion ROM at 00020000 [disabled]
         Capabilities: <available only to root>


  reply	other threads:[~2004-09-24 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24 15:03 reiserfs and SCSI oops seen in 2.6.9-rc2 with local SCSI disk IO David Wysochanski
2004-09-24 15:18 ` Matthew Wilcox
2004-09-24 15:42   ` David Wysochanski [this message]
2004-09-24 17:58     ` Christoph Hellwig
2004-09-27 20:44     ` Chris Mason
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=4154404B.3070705@netapp.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).