linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: brem belguebli <brem.belguebli@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM preference for multipath verses disk/by-id/scsi
Date: Mon, 4 Jan 2010 14:17:24 +0100	[thread overview]
Message-ID: <29ae894c1001040517sa6bb7f9v56915a22a820d2c4@mail.gmail.com> (raw)
In-Reply-To: <1262609658.18517.3.camel@localhost>

Hi,

Never had no problem with it.

The only problem I've hit was due to the binding file being, by
default, located in /var/lib/multipath, which is in my setup on a
separate LV than /, during boot time the devices were not correctly
created.

Just had to switch the binding file to /etc and now no more problem.

extract of my /etc/multipath.conf :


defaults {
...
        flush_on_last_del       yes
        user_friendly_names     yes
        bindings_file "/etc/multipath_bindings"
}

2010/1/4 Bryn M. Reeves <bmr@redhat.com>:
> On Wed, 2009-12-30 at 12:52 +0100, brem belguebli wrote:
>> Hi,
>>
>> see man 5 lvm.conf there is an option called preferred_names which is
>> well explained
>>
>> It'll instruct lvm to use the preferred_names you configured in the
>> lvm.conf file if they exist
>>
>> ie : preferred_names = "/dev/mpath/" will use /dev/mpath/XXX instead
>> of /dev/mapper/XXX
>
> It's best not to use the symlinks in /dev/mpath - they are not always
> reliable. Use the device nodes created in /dev/mapper instead.
>
> Regards,
> Bryn.
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

  reply	other threads:[~2010-01-04 13:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 10:18 [linux-lvm] LVM preference for multipath verses disk/by-id/scsi Simon Loewenthal/NL/Tele2
2009-12-30 10:31 ` Simon Loewenthal/NL/Tele2
2009-12-30 11:52   ` brem belguebli
2009-12-30 12:37     ` Simon Loewenthal/NL/Tele2
2009-12-30 12:40       ` Simon Loewenthal/NL/Tele2
2009-12-30 13:00       ` brem belguebli
2009-12-30 13:45         ` Simon Loewenthal/NL/Tele2
2009-12-30 14:15           ` Simon Loewenthal/NL/Tele2
2010-01-04 12:54     ` Bryn M. Reeves
2010-01-04 13:17       ` brem belguebli [this message]
2010-01-05 10:52         ` Simon Loewenthal/NL/Tele2
2010-01-05 11:25           ` Simon Loewenthal/NL/Tele2
2010-01-05 16:12             ` Simon Loewenthal/NL/Tele2
2010-01-11 14:12               ` Simon Loewenthal/NL/Tele2
2010-01-11 15:18                 ` Eugene Vilensky
2010-01-11 16:06                   ` Simon Loewenthal/NL/Tele2
2010-01-12  1:13                     ` Eugene Vilensky

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=29ae894c1001040517sa6bb7f9v56915a22a820d2c4@mail.gmail.com \
    --to=brem.belguebli@gmail.com \
    --cc=linux-lvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).