From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: scsi_id question
Date: Fri, 02 Nov 2007 04:44:59 +0000 [thread overview]
Message-ID: <200711020745.00243.arvidjaar@mail.ru> (raw)
In-Reply-To: <B6FF36386FC9AC4BB098A4528811409F452557@CORPUSMX40A.corp.emc.com>
[-- Attachment #1.1: Type: text/plain, Size: 1597 bytes --]
On Friday 02 November 2007, lemons_terry@emc.com wrote:
> Hi
>
> We've been observing the behavior of scsi_id, as a component of the udev
> machinery that creates persistent device names in the
> /dev/|generic|disk|tape/by-id directories. When scsi_id is run against a
> tape device that has more than one useful item in the VPD pages, scsi_id
> selects one of these items as the basis for the name that is generated.
> There is obviously some sort of hierarchy in play here. For instance, if a
> device has both a WWNN and a serial number, scsi_id will use the WWNN.
> That's a good choice, IMHO, given that modern tape libraries have WWNN
> assigned to the 'sled' that tape drives fit into When a tape drive is
> replaced, the serial number changes but the 'sled' WWNN stays the same (so
> I'm told).
>
> But if a device has both an IENN and a serial number, the IENN is used.
> And that's a bad choice, because the IENN is not unique.
But is not duplicated EUI-64 actually a bug that should be reported to vendor?
> I have a tape
> library in my lab that has two tape drives with the same IENN and different
> serial numbers. udev does not create a persistent device name for both of
> these tape drives. This is, to me, a bug.
>
> Can I/we get a peek at the hierarchy that scsi_id uses?
Sure. In udev sources :)
> Methinks some
> fine-tuning is necessary.
>
By default page 0x83 is tried first if available. You can force page 0x80
(serial number) when calling scsi_id or per vendor or per model
in /etc/scsi_id.config.
HTH
-andrey
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 226 bytes --]
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2007-11-02 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 0:08 scsi_id question lemons_terry
2007-11-02 4:44 ` Andrey Borzenkov [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=200711020745.00243.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).