All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: User friendly names patch.
Date: Tue, 25 Oct 2005 10:41:21 +0200	[thread overview]
Message-ID: <20051025084121.GA17494@free.fr> (raw)
In-Reply-To: <20051024164902.GB19176@phlogiston.msp.redhat.com>

> > One of my worry is that /var/lib/multipath/bindings is not available in
> > early userspace. Is this taken care of. Also remember not relying on
> > hotplug to execute multipath in early userspace is a redhat choice.
> > Others strategy may differ.
> 
> To make this work seamlessly with early userspace, You would need to add
> the correct /var/lib/multipath/bindings file to the initrd. The easiest work
> around to to simply stick the alias for that device in /etc/multipath.conf.
> 
> To make this work without editing the initrd or forcing people to have
> aliases in their config files, you would need to change multipath behavior.
> Currently, if multipath finds a device with the same wwid and a different
> alias, it removes the device and recreates it.  If it simply just left the
> device with the old name, then you would not get the benefit of user friendly
> names for devices that were started in early userspace, but you would not
> be any worse off than before. (Well, not quite. A binding would exist for the
> device in the bindings file, and if on some other boot, that multipath wasn't
> created in early userspace, when it got created it would use the name from
> the bindings file). This method would also require a command line option to
> override the "user_friendly_names" config file option in early userspace.
> 
ok,

let me know what you think of the following early userspace scenario sketch.
It aleviates the bindings sync issues between early and normal userspace.

Pre-requisites :
- no multipath config or binding files packaged in early userspace
- move bindings from /var to /etc

early userspace trace :
- load storage drivers
- path nodes are created
- lookup the rootdev wwid in a config file created at system install time or
  by init{ramfs,rd} rebuild script
- exec "multipath $wwid" : the scope limiting is the trick as only root dev
  map gets created. All defaults will apply : failover policy, etc ...
- mount /dev/mapper/$wwid
- pump config and bindings in early userspace namespace
- umount root fs
- exec "multipath $wwid" again
- deduce $alias from {bindings file & $wwid}
- mount /dev/mapper/$alias

Regards,
cvaroqui

  reply	other threads:[~2005-10-25  8:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21 23:35 User friendly names patch Benjamin Marzinski
2005-10-22  7:36 ` Christophe Varoqui
2005-10-24 15:23   ` Benjamin Marzinski
2005-10-22  7:52 ` Christophe Varoqui
2005-10-24 16:49   ` Benjamin Marzinski
2005-10-25  8:41     ` Christophe Varoqui [this message]
2005-10-25 19:17       ` Benjamin Marzinski
2005-10-25 19:37         ` Christophe Varoqui
2005-10-27  2:14           ` Benjamin Marzinski
2005-10-27  2:20             ` Benjamin Marzinski
2005-10-27  7:51               ` 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=20051025084121.GA17494@free.fr \
    --to=christophe.varoqui@free.fr \
    --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.