From: Patrick Mansfield <patmans@us.ibm.com>
To: "Josef Möllers" <josef.moellers@fujitsu-siemens.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Why REPORT LUN only for SCSI-2?
Date: Tue, 15 Jul 2003 07:39:27 -0700 [thread overview]
Message-ID: <20030715073927.A8218@beaverton.ibm.com> (raw)
In-Reply-To: <3F140D30.D2B5C4D8@fujitsu-siemens.com>; from josef.moellers@fujitsu-siemens.com on Tue, Jul 15, 2003 at 04:18:24PM +0200
On Tue, Jul 15, 2003 at 04:18:24PM +0200, Josef Möllers wrote:
> Hi,
>
> Ist there a hard reason not to allow the REPORT LUNS command for SCSI-2
> devices?
No.
> Are there actually some SCSI-2 devices which break on this command?
Probably, given the range of SCSI devices out there.
> There are several devices (e.g. RAID) which tread carefull and claim
> only SCSI-2 compliancy but support REPORT LUNS. It would make life
> easier with these if REPORT LUNS would be generally available.
> Eg I have a box which will happily accept INQUIRYs on LUNs 0-7 but
> REPORT LUNS returns only the 4 configured LUNs.
Are the unconfigured LUNs showing up as if they were configured?
Most disk/RAID arrays made in the last few years can configure whether
they report back as SCSI-2 or SCSI-3. It would be best if you could change
the device to report as SCSI-3.
Even some SCSI disk drives are capable of reporting back as SCSI-2 or
SCSI-3.
-- Patrick Mansfield
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-07-15 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 14:18 Why REPORT LUN only for SCSI-2? Josef Möllers
2003-07-15 14:39 ` Patrick Mansfield [this message]
2003-07-16 7:00 ` Josef Möllers
2003-07-16 19:35 ` Patrick Mansfield
2003-07-17 8:55 ` Josef Möllers
2003-07-17 18:49 ` Kurt Garloff
2003-07-17 23:46 ` Patrick Mansfield
2003-07-18 6:38 ` Josef Möllers
-- strict thread matches above, loose matches on Subject: below --
2003-07-18 0:25 David.Egolf
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=20030715073927.A8218@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=josef.moellers@fujitsu-siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox