From: "Philip R. Auld" <pauld@egenera.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Steven Dake <sdake@mvista.com>,
linux-scsi@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [announce] scsi_id 0.1 - generate unique scsi id
Date: Tue, 28 Oct 2003 10:40:54 -0500 [thread overview]
Message-ID: <20031028104054.K4263@vienna.EGENERA.COM> (raw)
In-Reply-To: <20031028070640.A8503@beaverton.ibm.com>; from patmans@us.ibm.com on Tue, Oct 28, 2003 at 07:06:40AM -0800
Rumor has it that on Tue, Oct 28, 2003 at 07:06:40AM -0800 Patrick Mansfield said:
> udev needs to somehow handle duplicates, but unless we tell it a
> device is multi-pathed, it can't tell an error case (tried to give the
> same name to two separate devices) from the multi-path case.
>
Does udev need to care about multi-pathing? I'm not sure that it does - it doesn't
do multi-pathing, it just makes device nodes, right?
It seems that if we want the underlying paths to show up as separate named devices
we would need to use an ID key that is different from the one that the multipath
detection code uses so that we do get the underlying paths. That's why I
suggested the below.
If it's the same ID key, we'd be relying on udev's duplicate handling behavior and
the results would likely be order dependent.
> > It may be that the way this is used best is to use it as a call out in udev
> > if you're not doing multi-path. Then if you are using MP, configure udev to
> > use scsi bus based names and have the MP detection script call out to scsi_id.
> > That's at least how I think I would set it up.
>
> That is one way to configure them. The current udev would need a lot of
> entries to handle all possible names - if you wanted to be able to add
> a new LUN or path and have it just show up with the path in its name.
>
I would have hoped for a setting to do that without having to configure each
individual possible entry. Something that made it work similar to the scsidev utility.
> Users might also want the name of the MP device to be similar to the
> names for the paths of the device. This means udev would need to be passed
> information that these are multi-pathed devices (assuming it would
> otherwise create only one entry).
>
Do md/dm devices get created by udev? Then the problem shows up again.
We'd get the md device named "disk-1" as well :)
Cheers,
Phil
--
Philip R. Auld, Ph.D. Technical Staff
Egenera Corp. pauld@egenera.com
165 Forest St., Marlboro, MA 01752 (508)858-2600
next prev parent reply other threads:[~2003-10-28 15:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 23:58 [announce] scsi_id 0.1 - generate unique scsi id Patrick Mansfield
2003-10-22 14:31 ` Christoph Hellwig
2003-10-22 7:42 ` Daniel Stekloff
2003-10-22 14:46 ` Christoph Hellwig
2003-10-22 8:05 ` Daniel Stekloff
2003-10-22 15:52 ` Matthew Wilcox
2003-10-22 16:15 ` Patrick Mansfield
2003-10-22 16:23 ` Christoph Hellwig
2003-10-23 7:33 ` Jes Sorensen
2003-10-24 21:33 ` Steven Dake
2003-10-27 14:16 ` Philip R. Auld
2003-10-27 15:27 ` Patrick Mansfield
2003-10-27 17:06 ` Philip R. Auld
2003-10-27 17:31 ` Patrick Mansfield
2003-10-28 14:19 ` Philip R. Auld
2003-10-28 15:06 ` Patrick Mansfield
2003-10-28 15:40 ` Philip R. Auld [this message]
2003-10-28 16:29 ` Patrick Mansfield
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=20031028104054.K4263@vienna.EGENERA.COM \
--to=pauld@egenera.com \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
--cc=sdake@mvista.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