From: christophe.varoqui@free.fr
To: linux-hotplug@vger.kernel.org
Subject: Re: Patch to multipath-tools 0.2.4
Date: Tue, 13 Jul 2004 08:17:04 +0000 [thread overview]
Message-ID: <1089706624.40f39a80acfa7@imp5-q.free.fr> (raw)
In-Reply-To: <40E92177.7000800@suse.de>
It sounds fair for scsi_id to try as hard as possible to generate a *really
unique* uid, thus the prefix.
In the context of multipath, do you suggest I introduce this prefix in the
fallback internal method or should I trim the scsi_id output ?
Subsidiary question : should I merge scsi_id in the multipath-tools tree for
klibc build ?
regards,
cvaroqui
Selon Patrick Mansfield <patmans@us.ibm.com>:
> On Mon, Jul 12, 2004 at 11:46:12PM +0200, christophe varoqui wrote:
> > On ven, 2004-07-09 at 18:00, Patrick Mansfield wrote:
> > > On Fri, Jul 09, 2004 at 05:50:23PM +0200, christophe varoqui wrote:
> > > >
> > > > That, or a libscsiid ...
> > > > Do you plan to produce such a lib ?
> > > >
> > >
> > > No plans, but have thought about it. A callout is simpler and more
> > > flexible, maybe slower but that should not be a issue.
> > >
> > ok, I got the callout working in my current tree.
>
> Thanks for doing that work.
>
> > before I release, I would like to report that scsi_id presents a strange
> > leading digit in its output.
> > In my case a wwid like 6005xxxxxxxxxxxx (32 char) becomes
> > 36005xxxxxxxxxxxx (33 char).
> >
> > Note it's a bit annoying because the fallback get_evpd_wwid (in case
> > scsi_id is absent) rightfully reports 64 bit uuid, which is not
> > consistant with scsi_id reporting.
> >
> > Can you explain this and give guidance ?
>
> The first digit is the value of the "identifier type", looking at the SCSI
> primary commands draft spc3r19, the values in table 284, section 7.6.4.1,
> page numbered 312.
>
> The different types of identifiers could in theory - though perhaps
> unlikely or maybe even impossible at this time - have overlapping name
> spaces.
>
> For example, the NAA IEEE extended has an 8 byte value (including the NAA
> type), as does the EUI-64 8 byte value (there are non 64 bit EUI-64
> values!?).
>
> The page 0x83 "identifier type" is 8 bits, and so can never overlap with
> the scsi_id page 0x80 prefix of 0x53 ('S'), so the scsi_id page 0x80
> values can never overlap with page 0x83 values.
>
> -- Patrick Mansfield
>
--
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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
next prev parent reply other threads:[~2004-07-13 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 9:37 Patch to multipath-tools 0.2.4 Hannes Reinecke
2004-07-05 12:11 ` christophe.varoqui
2004-07-09 15:32 ` Patrick Mansfield
2004-07-09 15:50 ` christophe varoqui
2004-07-09 16:00 ` Patrick Mansfield
2004-07-12 21:46 ` christophe varoqui
2004-07-13 0:26 ` Patrick Mansfield
2004-07-13 8:17 ` christophe.varoqui [this message]
2004-07-13 16:57 ` Patrick Mansfield
2004-07-14 9:49 ` christophe varoqui
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=1089706624.40f39a80acfa7@imp5-q.free.fr \
--to=christophe.varoqui@free.fr \
--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).