From: Patrick Mansfield <patmans@us.ibm.com>
To: Catalin Muresan <catalin.muresan@astral.ro>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org, bogdan.luca@astral.ro
Subject: Re: Apple Xserve RAID and qlogic ISP2312 (qla2300)
Date: Mon, 1 Nov 2004 11:48:45 -0800 [thread overview]
Message-ID: <20041101194845.GA27913@us.ibm.com> (raw)
In-Reply-To: <20041101105611.GJ22603@astral.ro>
[ resending ... not sure if this went out at all ]
On Mon, Nov 01, 2004 at 12:56:11PM +0200, Catalin Muresan wrote:
>
> I have the attached patch from Andrew which fixes the qla2300 part
> of the problem (attached) and a patch is still needed for the case where
> there are LUN0,3 to blacklist the device as BLIST_SPARSELUN.
No attachment ...
> > 2) If LUN 0 gets a DID_NO_CONNECT (and we do return the
> > SCSI_SCAN_NO_RESPONSE), we won't scan anything, via REPORT LUN or via
> > a sequential scan.
>
> we need to have something on LUN 0 to be able to send REPORT LUN, in
> this case we don't.
You don't need storage configured on LUN 0 to send it a REPORT LUN, if
there is a target there, you can (well should) be able to send it a REPORT
LUN.
You do need the driver to allow commands to be issued to LUN 0 (that is
what the patch should have fixed).
SCSI spec says:
A SCSI device shall support a REPORT LUNS command that is
addressed to logical unit zero. Support of the REPORT LUNS command
by logical units other than logical unit zero is optional.
> Do you need me to test some other stuff or we can "close" this
> issue?
In order of best to worst solutions:
If device supports REPORT LUNs:
1) configure the array to report as SCSI-3
2) black list as BLIST_REPORTLUN2
If no REPORT LUNs support:
3) black list as BLIST_SPARSELUN
-- Patrick Mansfield
next prev parent reply other threads:[~2004-11-01 19:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 23:33 Apple Xserve RAID and qlogic ISP2312 (qla2300) Catalin Muresan
2004-10-28 14:37 ` Patrick Mansfield
2004-10-28 15:35 ` Catalin Muresan
2004-10-28 16:42 ` Patrick Mansfield
2004-10-28 16:51 ` Patrick Mansfield
2004-10-28 17:21 ` Andrew Vasquez
2004-10-29 8:58 ` Catalin Muresan
2004-10-29 18:06 ` Patrick Mansfield
2004-10-30 15:44 ` Catalin Muresan
2004-11-01 10:56 ` Catalin Muresan
2004-11-01 19:48 ` Patrick Mansfield [this message]
2004-11-09 2:49 ` Report luns [was: Apple Xserve RAID and qlogic ISP2312 (qla2300)] Douglas Gilbert
2004-11-09 15:06 ` Luben Tuikov
2004-11-09 21:10 ` Patrick Mansfield
2004-11-09 22:07 ` Luben Tuikov
2004-11-10 4:47 ` Report luns Douglas Gilbert
2004-11-10 14:13 ` Luben Tuikov
2004-11-10 5:19 ` Report luns [was: Apple Xserve RAID and qlogic ISP2312 (qla2300)] Douglas Gilbert
2004-11-10 14:47 ` Luben Tuikov
2004-10-29 9:01 ` Apple Xserve RAID and qlogic ISP2312 (qla2300) Catalin Muresan
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=20041101194845.GA27913@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=andrew.vasquez@qlogic.com \
--cc=bogdan.luca@astral.ro \
--cc=catalin.muresan@astral.ro \
--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.