public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Tom Coughlan <coughlan@redhat.com>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
	EXT / DEVOTEAM VAROQUI Christophe <ext.devoteam.varoqui@sncf.fr>,
	"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
	linux-scsi-owner@vger.kernel.org,
	Martin Peschke3 <MPESCHKE@de.ibm.com>,
	"Robert J. Adams (jason)" <radams@siscom.net>
Subject: Re: Mount by WWN (FC, using qlogic 2200)
Date: 05 Feb 2004 10:10:29 -0500	[thread overview]
Message-ID: <1075993831.1756.8.camel@mulgrave> (raw)
In-Reply-To: <1075989386.19275.1895.camel@bianchi.boston.redhat.com>

On Thu, 2004-02-05 at 08:56, Tom Coughlan wrote:
> Each identifier on the SPC-3 Device Identification VPD page (page 83)
> has an "association" field, with one of the following values:
> 
> - The IDENTIFIER field is associated with the addressed logical unit. 
> - The IDENTIFIER field is associated with the SCSI target port that
> received the request. 
> - The IDENTIFIER field is associated with the SCSI target device that
> contains the addressed logical unit. 
> 
> So, an identifier on page 83 may be either an LU WWN, WWPN, or a WWNN. 

Actually, this isn't an either/or, the page may contain a list. 
However, the standard is very clear (7.6.4.11.3) that each LUN that is
not a well known LUN shall have at least one identifier of association 0
(Logical Unit Identifier).

> We need to check the association field, and use the identifier
> appropriately, and we need to insist that storage vendors implement it
> correctly.

I agree, but I see this as a userspace issue.

James



  reply	other threads:[~2004-02-05 15:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OFB4AE9EAB.C15E2C56-ON87256E30.007E8F0D-88256E30.007F5E0C@us.ibm.com>
2004-02-04 23:23 ` Mount by WWN (FC, using qlogic 2200) James Bottomley
2004-02-05  0:33   ` Bryan Henderson
2004-02-05 13:56     ` Tom Coughlan
2004-02-05 15:10       ` James Bottomley [this message]
2004-02-05 16:38         ` Patrick Mansfield
2004-02-05  9:52 EXT / DEVOTEAM VAROQUI Christophe
  -- strict thread matches above, loose matches on Subject: below --
2004-02-04 19:58 Martin Peschke3
2004-02-04 20:06 ` James Bottomley
2004-02-04 20:15   ` Patrick Mansfield
2004-02-04 10:19 EXT / DEVOTEAM VAROQUI Christophe
2004-02-04 18:39 ` Robert J. Adams (jason)
2004-02-04  1:27 NH Support

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=1075993831.1756.8.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=MPESCHKE@de.ibm.com \
    --cc=coughlan@redhat.com \
    --cc=ext.devoteam.varoqui@sncf.fr \
    --cc=hbryan@us.ibm.com \
    --cc=linux-scsi-owner@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=radams@siscom.net \
    /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