All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] [RFC] persistent readable names
Date: Thu, 6 Oct 2005 08:54:31 -0700	[thread overview]
Message-ID: <20051006155431.GA9285@us.ibm.com> (raw)
In-Reply-To: <4344CD38.2030004@redhat.com>

Hi Patrick :)

On Thu, Oct 06, 2005 at 08:07:36AM +0100, Patrick Caulfield wrote:
> Patrick Mansfield wrote:
> 
> > Here is some /dev, lsscsi and scsi_id output on a SLES9 system (rpm
> > udev-021-36.55). by-path is basically pci and scsi bus_id's; by-id is
> > basically scsi_id plus partition output. 
> > 

> Those are the names I'm trying to free people from.
> 
> OK, multipath1 - multipath5000 aren't exactly friendly (but how else are you
> going to name 5000 disks - there aren't that many Simpsons characters!) but
> they're are a /lot/ easier to deal with than those I can see there.

But we should not have a dm only solution.

For that many disks, I don't see how it helps much, you must still deal
with the specific id's at some level. I was thinking more about nice names
for a few disks, or splitting disks into groups with a common prefix (and
then still keep the long id portion).

Enumerating names in shared/cluster setups probably makes things worse,
though you could try to share or copy the file that maps wwid to the
enumeration, the same thing for a udev solution.

-- Patrick Mansfield

  reply	other threads:[~2005-10-06 15:54 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
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 [this message]
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=20051006155431.GA9285@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.