public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <praka@users.sourceforge.net>
To: Yann Dupont <Yann.Dupont@univ-nantes.fr>
Cc: linux-scsi@vger.kernel.org
Subject: Re: puzzling scsi return code 20000
Date: Tue, 6 Jul 2004 11:46:26 -0700	[thread overview]
Message-ID: <20040706184626.GA30970@praka.san.rr.com> (raw)
In-Reply-To: <40E9448F.1090700@univ-nantes.fr>

On Mon, 05 Jul 2004, Yann Dupont wrote:

> hello. I have some problems with a SAN here. Don't know if the problems 
> lies in scsi code/driver or other thing...
> 
> The setup is :
> a QLA2300 (Fibre channel) with 6.0.64 driver from qlogic site,
>

I'm not familiar with that version number (are you sure it's 6.0.64,
perhaps 6.06.64?).  I believe the latest driver submitted to DVT has
been posted to the website (7.00.03).

> 2.4.26 kernel, device mapper 1.0.17 applied,
> and xfs or reiserfs on top of lvm volumes (using evms)
> 
> This setup seemed fine since some months now, with giga of data moved 
> every day, but I noticed this on the log:
> 
> Jun 22 16:45:15 talisker kernel: SCSI disk error : host 3 channel 0 id 2 
> lun 1 return code = 20000
> Jun 22 16:45:15 talisker kernel:  I/O error: dev 08:10, sector 145423312
> 
> I have two of these errors in the last month. What's the meaning of this 
> return code ? I made
> badblock on the /dev/evms volume, and all is OK.
>

20000 == DID_BUS_BUSY -- one possibility, the QLogic driver returned a
command with the status, mid-layer ran out of retries, subsequently
returning the status to the upper-layer driver.  But that doesn't
help in finding out what went wrong.

> I also performed a disk scan on the raid array, (an IFT 7250F) and there 
> are no errors.
> 
> The machine can be quite heavily loaded. May I suspect the qla driver ? 
> May I suspect the underlying LVM. The LVM has been resized by the 
> past... Can an error happens here too ?
> I'm very puzzled...
> 
> This is just a summary . I can furnish more information if needed.
> 

I'd suggest you try a more recent driver (noted above), if the I/O
errors persist, then report the problem to tech-support at:

	http://connection.qlogic.com/support/report/index.asp?id=csg

with a complete description.

Regards,
Andrew Vasquez
QLogic Corporation

  reply	other threads:[~2004-07-06 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05 12:07 puzzling scsi return code 20000 Yann Dupont
2004-07-06 18:46 ` Andrew Vasquez [this message]
2004-07-07 10:04   ` Yann Dupont
2004-07-09  9:21     ` Yann Dupont
2004-07-09 14:57       ` Andrew Vasquez
2004-07-29 16:11   ` Yann Dupont

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=20040706184626.GA30970@praka.san.rr.com \
    --to=praka@users.sourceforge.net \
    --cc=Yann.Dupont@univ-nantes.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox