linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Patrick Mansfield <patman@aracnet.com>
Cc: Chris Paulson-Ellis <chris@edesix.com>,
	Bill Nottingham <notting@redhat.com>,
	linux-hotplug-devel@lists.sourceforge.net,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	jgarzik@pobox.com
Subject: Re: [PATCH] /dev/disk/by-id incomplete and unhelpful for SATA drives
Date: Sat, 07 Jan 2006 09:44:55 +1000	[thread overview]
Message-ID: <43BF00F7.9010104@torque.net> (raw)
In-Reply-To: <20060106194652.GB6404@aracnet.com>

Patrick Mansfield wrote:
> On Fri, Jan 06, 2006 at 10:39:34PM +1000, Douglas Gilbert wrote:
> 
<snip>
> 
> I was trying to figure out if we are guranteed will have unique values
> across all ATA devices with Doug's patch. I am not familiar with ATA and
> IDENTIFY DEVICE.

http://www.t13.org/docs2005/D1699r2a-ATA8-ACS.pdf
is the most recent draft of the ATA-8 command set.

> For page 0x83, Doug's change above gives us:
> 
> 	ATA + 40 bytes of model/product (must have white space) + serial number
> 
> Under "10.3.4.2.3 Logical unit name derived from the model number and
> serial number" the spec says:
> 
> 	NOTE 9 The logical unit name using the T10 vendor identification
> 	format is not guaranteed to be worldwide unique, since ATA/ATAPI-7
> 	only requires the combination of the MODEL NUMBER field and SERIAL
> 	NUMBER field to be unique for a given manufacturer but defines no
> 	manufacturer identification field.
> 
> I don't know why they have this given the above. So it is possible (though
> unlikely?) that model numbers will overlap, and so scsi_id values too?

Unlikely but two vendors could use the same model and
serial numbers.

> If we put had an actual vendor in the sdev->vendor, we could use page 0x83
> type 0 with no name collisions (if that vendor + model actually gives us
> unique serial numbers). 
> 
> Why does the SAT translation spec have the vendor identification of ATA???

I guess because there is no requirement for a manufacturer
of (s)ATA disks to have a registered t10 vendor id ...
IEEE wants money for OUI registrations, t10 probably wants
money for a t10 vendor id, t13 probably wants money etc ...
BTW As I have mentioned in the past, linux probably should
have a OUI registration (paid by whom??).

> The "logical unit name derived from the world wide name" looks nicer, but I
> assume not all vendors support that.

Yes and not yet, until it becomes mandatory, if ever. ATA8-ACS shows
a naa-5 (8 byte, 4 word) identifier
starting at word 108 in the IDENTIFY DEVICE response. I like the
ACS wording: "Words 111-108 shall contain the optional value of the
world wide name"! The "shall" implies it is mandatory but obviously
the "optional" doesn't. Perhaps it was written by a lawyer :-)

We probably could and should add the naa-5 designator in VPD
page 0x83, perhaps dependent on whether there is a 0x5 in
word 108 bits 15-12 . For example, an old-ish Seagate ST380013AS
sata disks has zero in those 8 bytes.

Perhaps others could check their sata disks and report back if
any have a real naa-5 wwn starting at word 108. ["sg_inq -AH"
on a (s/p)ATA disk will dump the IDENTIFY DEVICE response in hex.]

Doug Gilbert


  reply	other threads:[~2006-01-06 23:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <doc5jl$acv$1@sea.gmane.org>
     [not found] ` <20051221185518.GA9100@vrfy.org>
     [not found]   ` <43A9CFE0.2070103@edesix.com>
     [not found]     ` <20051222043527.GA13175@vrfy.org>
     [not found]       ` <43AA8D0B.10504@edesix.com>
     [not found]         ` <20051222183525.GA17871@devserv.devel.redhat.com>
     [not found]           ` <43AB40E2.1050009@edesix.com>
2006-01-06  1:36             ` /dev/disk/by-id incomplete and unhelpful for SATA drives patman
2006-01-06  2:57               ` Douglas Gilbert
2006-01-06 12:39                 ` [PATCH] " Douglas Gilbert
2006-01-06 13:34                   ` Chris Paulson-Ellis
2006-01-06 18:58                     ` Patrick Mansfield
2006-01-06 19:46                   ` Patrick Mansfield
2006-01-06 23:44                     ` Douglas Gilbert [this message]
2006-03-06 20:08                   ` Jeff Garzik
2006-03-07 17:05                     ` Douglas Gilbert

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=43BF00F7.9010104@torque.net \
    --to=dougg@torque.net \
    --cc=chris@edesix.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=notting@redhat.com \
    --cc=patman@aracnet.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;
as well as URLs for NNTP newsgroup(s).