All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: linux-scsi@vger.kernel.org
Subject: Weird SCSI error, can anyone interpret?
Date: Wed, 03 Mar 2004 21:06:44 -0700	[thread overview]
Message-ID: <4046AB54.9010909@backtobasicsmgmt.com> (raw)

I've got a client with a server running 2.6.3-rc2, using a QLogic 
ISP2100 connected to a CMD FC-to-SCSI RAID controller. On Saturday 
morning, the system lost access to the RAID array, with thousands of 
messages like these in the log:

Feb 28 03:15:46 alpha kernel: SCSI error : <2 0 0 0> return code = 0x20000
Feb 28 03:15:46 alpha kernel: end_request: I/O error, dev sdc, sector 
278362544
Feb 28 03:15:51 alpha kernel: SCSI error : <2 0 0 0> return code = 0x20000
Feb 28 03:15:51 alpha kernel: end_request: I/O error, dev sdc, sector 
304356160
Feb 28 03:16:06 alpha kernel: SCSI error : <2 0 0 0> return code = 0x20000
Feb 28 03:16:06 alpha kernel: end_request: I/O error, dev sdc, sector 
360710592
Feb 28 03:16:06 alpha kernel: SCSI error : <2 0 0 0> return code = 0x20000
Feb 28 03:16:06 alpha kernel: end_request: I/O error, dev sdc, sector 
327384736

There are also some with "return code = 0x20008".

Restarting the Linux system did not help; power cycling the RAID array 
did help. I'd like to get some clue as to whether this points to a 
problem with the RAID controller, the FC host adapter, or the kernel's 
QLogic driver. This system had been previously using the QLogic driver 
from SourceForge for months on a 2.6.0-pre(something) kernel, but 
recently got upgraded once the QLogic driver was merged into the main 
kernel distribution.

Please CC me on any replies, I'm not subscribed to linux-scsi. Thanks!

             reply	other threads:[~2004-03-04 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  4:06 Kevin P. Fleming [this message]
2004-03-05  6:07 ` Weird SCSI error, can anyone interpret? Andrew Vasquez
2004-03-05 14:47   ` Kevin P. Fleming

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=4046AB54.9010909@backtobasicsmgmt.com \
    --to=kpfleming@backtobasicsmgmt.com \
    --cc=linux-scsi@vger.kernel.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.