From: James Bottomley <James.Bottomley@SteelEye.com>
To: "conway, heather" <conway_heather@emc.com>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: RE: Request to add EMC Invista to the v2.6.x SCSI Blacklist...
Date: Thu, 11 Aug 2005 11:39:08 -0500 [thread overview]
Message-ID: <1123778348.5062.27.camel@mulgrave> (raw)
In-Reply-To: <FA2F59D0E55B4B4892EA076FF8704F5509DDC99C@SRGRAHAM.eng.emc.com>
On Thu, 2005-08-11 at 11:45 -0400, conway, heather wrote:
> The information that I was provided is that the default for the Invista is
> to report back as SCSI-3 compliant.
> Hope this helps.
Well, actually, now I'm confused. REPORT_LUNS is mandatory for a SCSI3
compliant device, and if the device reports SCSI-3 compliance we
automatically try a REPORT LUNS scan, which should mean that
BLIST_LARGE_LUN and BLIST_SPARSE_LUN are unnecessary, since we add all
LUNs returned by the scan (up to the limit of the HBA).
Could we try debugging this device to find out what its problem is?
James
next prev parent reply other threads:[~2005-08-11 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 15:45 Request to add EMC Invista to the v2.6.x SCSI Blacklist conway, heather
2005-08-11 16:39 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-15 20:33 conway, heather
2005-07-27 14:22 conway, heather
2005-07-30 15:00 ` James Bottomley
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=1123778348.5062.27.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=conway_heather@emc.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