From: Patrick Mansfield <patmans@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] [RFC] persistent readable names
Date: Wed, 5 Oct 2005 11:07:21 -0700 [thread overview]
Message-ID: <20051005180721.GA22387@us.ibm.com> (raw)
In-Reply-To: <20051005150923.GC6195@free.fr>
On Wed, Oct 05, 2005 at 05:09:23PM +0200, Christophe Varoqui wrote:
> On Wed, Oct 05, 2005 at 03:14:52PM +0100, Patrick Caulfield wrote:
> > This patch is more for discussion than inclusion at the moment. Basically it's
> > unrealistic for users with hundreds of disks to alias them all in
> > /etc/multipath.conf and the default names are very unwieldy.
> >
> > What this patch does is attach a name to any un-aliased path and write that name
> > to /etc/multipath.names. The file is read again every time the paths are added
> > so they are persistent.
I haven't recently looked at dm or dm multipath naming, but dm and dm
multipath should not have a different naming scheme outside of udev.
udev now has persistent naming, and probably could or should have a dm_id
(dm_id could run scsi_id on a single path, unless dm is passing down scsi
ioctl's). The udev persistent naming scheme is not intuitive (i.e. not
easy for people to create and use).
Intuitive names could be built upon the persistent names as part of udev,
like an alias, or if you could "match" a NAME, and have a new udev rule
like:
NAME=="disk/by-id/foo" SYMLINK+="disk/by-simple/my-database"
I hesitate to bring this up on the appropriate list, here:
linux-hotplug-devel@lists.sourceforge.net
without any patches :-/
-- Patrick Mansfield
next prev parent reply other threads:[~2005-10-05 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 14:14 [PATCH] [RFC] persistent readable names Patrick Caulfield
2005-10-05 15:09 ` Christophe Varoqui
2005-10-05 18:07 ` Patrick Mansfield [this message]
2005-10-05 21:27 ` Christophe Varoqui
2005-10-05 22:38 ` Patrick Mansfield
2005-10-06 7:07 ` Patrick Caulfield
2005-10-06 15:54 ` Patrick Mansfield
2005-10-06 7:04 ` Patrick Caulfield
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=20051005180721.GA22387@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=dm-devel@redhat.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 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.