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: Wed, 16 Jul 2003 12:35:19 -0700 [thread overview]
Message-ID: <20030716123519.A19244@beaverton.ibm.com> (raw)
In-Reply-To: <3F14F7FA.BA551505@fujitsu-siemens.com>; from josef.moellers@fujitsu-siemens.com on Wed, Jul 16, 2003 at 09:00:10AM +0200
On Wed, Jul 16, 2003 at 09:00:10AM +0200, Josef Möllers wrote:
> Patrick Mansfield wrote:
> 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.
But some broken devices might hang when sent a REPORT LUN command, and
then we have to add a BFLAGS_NO_REPORT_LUN or some other hacks.
We could change BLIST_LARGELUN to be BLIST_SCSI_3, and take that to mean
use REPORT LUN, and go up to the LLDD's max_lun (though I dislike adding
anything to the device_info table, especially when these devices should
report back as SCSI-3). Any multi-lun device that wants LUN > 8 better not
hang on a REPORT LUN.
> > Are the unconfigured LUNs showing up as if they were configured?
>
> Yes
Are the PQ values of the extra drives coming back as 1? If so the devices
will show up under sd but be offline. I can resend a patch for this, I got
no comments last time it went out.
You can easily tell if run with scsi scan logging, either boot with:
scsi_mod.scsi_logging_level=0x00000180
Or before insmod of the adapter:
echo scsi log scan 6 >/proc/scsi/scsi
> > 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.
For linux 2.6 SCSI-3 (generally) means we will send a REPORT LUN, and we
will allow sequential scans past lun 8, and that would be fine in your
case.
You mean making the device BLIST_SPARSELUN in the scsi_static_device_list
or device_info gives you 128 LUNs?
-- 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-16 19:20 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
2003-07-16 19:35 ` Patrick Mansfield [this message]
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=20030716123519.A19244@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 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.