All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: dgilbert@interlog.com,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	SCSI development list <linux-scsi@vger.kernel.org>
Cc: "Knight, Frederick" <Frederick.Knight@netapp.com>
Subject: Re: T10 adds locally assigned UUID designation descriptor
Date: Tue, 9 Feb 2016 16:30:11 +0100	[thread overview]
Message-ID: <56BA0603.1040003@suse.de> (raw)
In-Reply-To: <56B8F4BE.6050700@interlog.com>

On 02/08/2016 09:04 PM, Douglas Gilbert wrote:
> On 16-02-08 02:00 PM, James Bottomley wrote:
>> On Mon, 2016-02-08 at 12:33 -0500, Douglas Gilbert wrote:
>>> Recently, in draft spc5r08, T10 added a locally assigned RFC 4122
>>> UUID *** designation descriptor. That descriptor can now be
>>> returned for VPD page 0x83 (device identification) amongst others.
>>> It can be used anywhere SCSI needs a unique identifier expanding
>>> the previous set of preferred identifiers: EUI, NAA and SCSI_name
>>> (iSCSI).
>>>
>>> In the soon to be released sg3_utils version 1.42 the new UUID
>>> designation descriptor is decoded including Hannes' --export
>>> option found in sg_inq, for example:
>>>
>>> # sg_inq --export /dev/sg0
>>>     ...
>>>     SCSI_IDENT_LUN_UUID=11223344-5566-7788-aabb-ccddeeffffee
>>>
>>> Perhaps some udev work is needed to incorporate this new identifier.
>>
>> Hm, we're going to have to do this carefully.  With the move to GPT
>> partitions, both the UUID= designator in fstab and the /dev/disk/by
>> -uuid/ of udev means the GPT UUID.  In theory the design of the UUID
>> space is to allow random selection without clashing, so we could just
>> place the SCSI ones in here as well and perhaps there won't be a
>> problem, but I'd like us to think about the consequences first.
> 
> The UUID proposal (16-005r1 from Fred Knight and "Dr. Hannes Reinecke")
> was somewhat controversial with five T10 members voting against it. The
> minutes state: "The members voting no stated concern that this proposal
> may result in market confusion, and those members intend to develop
> proposals to mitigate any confusion."
> 
> Locally assigned identifiers are not new: there already is an 8 byte
> locally assigned NAA identifier (NAA=3). It is not much used, perhaps
> the new locally assigned UUID (which is 16 bytes long) will find
> more use. As for the 'sg_inq --export' naming, that seems to nail
> down the context of the new UUID pretty well:
>   SCSI_IDENT_[TARGET|PORT|LUN]_UUID
> with the identifier itself in canonical UUID format. So there should
> be no confusion there. And partitions are nested inside logical
> units and SCSI does not define those (apart from on tapes).
> 
Precisely.

These uuids will show up under /dev/disk/by-id
(as this is a hardware ID coming from the device).
So the existing UUID= or /dev/disk/by-uuid won't be influenced.
And UUID handling is confusing already (with basically every
subsystem providing one), so adding one more won't matter much :-)

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
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

      parent reply	other threads:[~2016-02-09 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 17:33 T10 adds locally assigned UUID designation descriptor Douglas Gilbert
2016-02-08 19:00 ` James Bottomley
2016-02-08 20:04   ` Douglas Gilbert
2016-02-09  0:02     ` Knight, Frederick
2016-02-09 15:30     ` Hannes Reinecke [this message]

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=56BA0603.1040003@suse.de \
    --to=hare@suse.de \
    --cc=Frederick.Knight@netapp.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dgilbert@interlog.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.