From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Bernd Schubert <bs@q-leap.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: what is return code 70000
Date: Wed, 16 Jan 2008 12:27:43 -0600 [thread overview]
Message-ID: <1200508063.3136.17.camel@localhost.localdomain> (raw)
In-Reply-To: <200801161913.24753.bs@q-leap.de>
On Wed, 2008-01-16 at 19:13 +0100, Bernd Schubert wrote:
> Hi,
>
> I already grepped, but I don't find the definition of
>
> return code = 0x00070000
>
>
> Just got with FC and 2.4.18 of scientitfic linux:
>
> sd 1:0:0:0: SCSI error: return code = 0x00070000
> end_request: I/O error, dev sdb, sector 294388752
> device-mapper: multipath: Failing path 8:16.
> sd 1:0:1:0: SCSI error: return code = 0x00070000
> end_request: I/O error, dev sdc, sector 1713114128
> device-mapper: multipath: Failing path 8:32.
> sd 2:0:1:0: SCSI error: return code = 0x00070000
> end_request: I/O error, dev sde, sector 2094272016
> device-mapper: multipath: Failing path 8:64.
>
>
> Since I have some error handling patches in queue for 2.6.22, I would like to
> know if I would have catched this error, but 0x00070000 is pretty meaningless
> for me :(
SCSI returns are 32 bit numbers with definitions in include/scsi/scsi.h
going (from lowest to highest)
1. status byte: the status return code from the command if
successfully executed
2. message byte: now misnamed, message is SPI specific, what it
means is task status interlaced with possible SPI message
responses.
3. host byte: these are the DID_ codes, specific error codes
returned by drivers.
4. driver byte: Additional qualification of the error in host byte
In your case, it's showing DID_ERROR.
James
next prev parent reply other threads:[~2008-01-16 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 18:13 what is return code 70000 Bernd Schubert
2008-01-16 18:27 ` James Bottomley [this message]
2008-01-16 19:05 ` Bernd Schubert
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=1200508063.3136.17.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=bs@q-leap.de \
--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.