From: "Josef Möllers" <josef.moellers@fujitsu-siemens.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Why REPORT LUN only for SCSI-2?
Date: Wed, 16 Jul 2003 09:00:10 +0200 [thread overview]
Message-ID: <3F14F7FA.BA551505@fujitsu-siemens.com> (raw)
In-Reply-To: 20030715073927.A8218@beaverton.ibm.com
Patrick Mansfield wrote:
> > Ist there a hard reason not to allow the REPORT LUNS command for SCSI-2
> > devices?
> No.
So, can I cast my vote to drop it? Or at least change it to a check for
SCSI_1.
The code does work with SCSI-2 devices (some disks) which don't support
REPORT LUNs and IMHO devices which do support command code A0h for
anything other than REPORT LUNs _are_ broken.
> > 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?
Yes
These are the configured entries from /proc/scsi/scsi:
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: MYLEX Model: DAC960FL 18000T0 Rev: 5426
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 01
Vendor: MYLEX Model: DAC960FL 18000T0 Rev: 5426
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 02
Vendor: MYLEX Model: DAC960FL 18000T0 Rev: 5426
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 03
Vendor: MYLEX Model: DAC960FL 15464T0 Rev: 5426
Type: Direct-Access ANSI SCSI revision: 02
These are the unconfigured LUNs:
Host: scsi1 Channel: 00 Id: 01 Lun: 04
Vendor: MYLEX Model: DAC960FL Rev: 5426
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 05
Vendor: MYLEX Model: DAC960FL Rev: 5426
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 06
Vendor: MYLEX Model: DAC960FL Rev: 5426
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 07
Vendor: MYLEX Model: DAC960FL Rev: 5426
Type: Direct-Access ANSI SCSI revision: 02
These last 4 Luns are not detected if I remove the SCSI_3 check at the
beginning of scsi_report_lun_scan().
> 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.
No, unfortunately we cannot change this. I've tried, but the vendors
(these are OEM parts, it's not only the MYLEX thingies shown above)
refused.
I guess (I haven't dug into this deep enough, I'm not a standards
person) is that the parts aren't 100% SCSI-3, connected to a
FibreChannel HA. They are capable of addressing more than 8 LUNs.
Adding them to the device_table doen't really work, because then we get
128 LUNs showing up and I have seen pretty large configurations with
several RAID boxes connected so we run out of device numbers.
Josef
--
Josef Möllers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
-
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-16 6:44 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
2003-07-16 7:00 ` Josef Möllers [this message]
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=3F14F7FA.BA551505@fujitsu-siemens.com \
--to=josef.moellers@fujitsu-siemens.com \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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.