From: Ewan Milne <emilne@redhat.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: Ramesh Chikkanayakanahally <rcnagara@Brocade.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"jbottomley@parallels.com" <jbottomley@parallels.com>
Subject: RE: Question on SCSI target scan
Date: Mon, 18 Nov 2013 12:28:32 -0500 [thread overview]
Message-ID: <1384795712.3839.6.camel@localhost.localdomain> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B4029547B9343@G9W0745.americas.hpqcorp.net>
On Fri, 2013-11-15 at 23:53 +0000, Elliott, Robert (Server Storage)
wrote:
> Beware that just because the LUN inventory is the same doesn't mean
> the logical units are the same. A logical unit at LUN X might have been
> deleted and another logical unit created and assigned to LUN X, but
> now containing different content. You need to check the logical unit
> name (in the Device Identification VPD page) too.
> ---
> Rob Elliott HP Server Storage
>
If the properties of the volume behind a particular LUN are changed,
shouldn't something like ASC/ASCQ 3F 03 INQUIRY DATA HAS CHANGED,
3F 04 DEVICE IDENTIFIER CHANGED be reported? Or can we not expect
this if a LUN is removed and then re-added without an intervening
REPORT LUNS command? (In that case, the REPORT LUNS data returned
will be no different.)
-Ewan
next prev parent reply other threads:[~2013-11-18 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 14:10 Question on SCSI target scan Ramesh Chikkanayakanahally
2013-11-15 23:53 ` Elliott, Robert (Server Storage)
2013-11-18 7:52 ` Ramesh Chikkanayakanahally
2013-11-18 15:28 ` James Bottomley
2013-11-18 17:28 ` Ewan Milne [this message]
2013-11-21 17:37 ` Elliott, Robert (Server Storage)
2013-11-21 18:45 ` Ewan Milne
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=1384795712.3839.6.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=Elliott@hp.com \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rcnagara@Brocade.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox