From: Brian King <brking@us.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Recognize missing LUNs for non-standard devices
Date: Tue, 07 Feb 2006 09:16:58 -0600 [thread overview]
Message-ID: <43E8B9EA.7050707@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0602070952410.5164-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Mon, 6 Feb 2006, Brian King wrote:
>
>> Alan Stern wrote:
>>> Some protocols (like USB UFI) or devices that don't adhere to the SCSI
>>> standard may indicate a nonexistent LUN by returning INQUIRY information
>>> with Peripheral Device Type set to 0x1f (unknown or none) and Peripheral
>>> Qualifier set to 0 instead of 3 as the spec requires. This patch (as650)
>>> causes PDT = 0x1f to be recognized as no LUN present regardless of the
>>> qualifier value, if the SCSI level is equal to 0.
>> This patch will break the ipr driver. The ipr adapter firmware reports a
>> logical scsi device which is used for RAID configuration. It reports
>> a Peripheral Device Type of 0x1f and a scsi level of 0, since it does
>> not claim compliance with any scsi level.
>
> I was afraid that might happen. Okay, forget the patch.
>
> How come you didn't mention the ipr driver before when I first raised the
> possibility of making this change?
Sorry about that... I wanted to verify on my end that the scsi level getting
returned was 0 before doing so. Your repost was a reminder...
Brian
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2006-02-07 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 21:59 [PATCH] Recognize missing LUNs for non-standard devices Alan Stern
2006-02-06 22:55 ` Brian King
2006-02-07 14:53 ` Alan Stern
2006-02-07 15:16 ` Brian King [this message]
2006-02-07 15:29 ` Alan Stern
2006-02-07 15:40 ` Brian King
2006-02-09 20:26 ` Alan Stern
2006-02-07 20:44 ` David Wysochanski
2006-02-07 21:22 ` Alan Stern
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=43E8B9EA.7050707@us.ibm.com \
--to=brking@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.