All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Changing SAN vendors
Date: Fri, 13 Feb 2009 10:28:47 +0000	[thread overview]
Message-ID: <49954B5F.5080209@redhat.com> (raw)
In-Reply-To: <4905EFD192EEDF4A9A19EEE98C32B7F70F3EB744@DBQV3005.na.corp.mckesson.com>

Allen, Jack wrote:
> Hello:
>     Still looking for an answer for RH AS 4.7.
>  
>     No body has any ideas?

The mpath names change because the XP is exporting the storage with 
new WWIDs (multipath-tools name binding is all based on LUN WWIDs). 
The bindings are stored in a file that is normally automatically 
generated and maintained.

I think in your stiuation if you need to preserve the old names, your 
best option is to manually edit the bindings file and copy it between 
the hosts that need to have a common view of the storage.

The default location for the file is /var/lib/multipath/bindings, 
although if you have /var configured as a separate file system you 
should move it to /etc and configure the bindings_file option in 
multipath.conf to avoid problems when initialising multipath devices 
before /var is mounted.

You could also take the steps that Tore suggested and configure 
multipath entries in multipath.conf to map the devices but unless you 
are happy with giving them new names this isn't going to work as the 
current multipath-tools will give undefined behaviour if you use 
"mpathN" style names for aliases defined in multipath.conf.

Regards,
Bryn.

  reply	other threads:[~2009-02-13 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 23:44 Changing SAN vendors Allen, Jack
2009-02-05 22:03 ` Allen, Jack
2009-02-06  7:41   ` Tore Anderson
2009-02-13  0:03   ` Allen, Jack
2009-02-13 10:28     ` Bryn M. Reeves [this message]
2009-02-13 22:47       ` Allen, Jack

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=49954B5F.5080209@redhat.com \
    --to=bmr@redhat.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.