All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chandra Seetharaman <sekharan@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Multipath Usage Guide available at LVM wiki page
Date: Thu, 24 Jan 2008 18:32:20 -0800	[thread overview]
Message-ID: <1201228340.2634.43.camel@linuxchandra> (raw)
In-Reply-To: <20080125021429.GC28785@us.ibm.com>

On Thu, 2008-01-24 at 18:14 -0800, malahal@us.ibm.com wrote:
> Chandra Seetharaman [sekharan@us.ibm.com] wrote:
> > On Thu, 2008-01-24 at 10:33 -0800, Pradipmaya Maharana wrote:
> > > Hi Chandra,
> > > 
> > > Thanks for the document, it surely is helpful.
> > > 
> > > I had a query (which I have asked in previous mails), the document
> > > does not talk about how to install SLES on multipath devices with LVM.
> > > Basically I tried installing with creating partitions (for both RHEL
> > > and SLES) and it worked fine; LVM worked fine for RHEL but for SLES it
> > > won't work.
> > > 
> > > - It won't let me mount-by device-id for LVM
> > > - specifying the volume label won't help.
> 
> Are you saying it won't help or it did NOT help?
> 
> > You could put your lvm on top of the multipathed dm-device. For which
> > you may have to disable lvm probing in the initrd phase. You can do this
> > by changing your /etc/lvm/lvm.conf and then running mkinitrd.
> > 
> > You have to change the filter line to be like this:
> > 
> > filter = [ "a|/dev/mapper.*|", "a|/dev/disk/by-name/.*|", "r|.*|" ]
> > 
> > Let me know if this helps.
> 
> multipath should be run before lvm (even in initrd), if so, how does
> this filter help?  LVM will not be able to claim plain devices in the
> presence of multipath devices anyway, right?

It can. I have seen it happen (in sles9 though). multipath opens the
(sd) device and later lvm scans the same device, it fails (as there is
already an open reference). 

The filter above helps in making lvm read the multipathed device instead
of the underlying scsi device, and hence the lvm scan succeeds.

> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
-- 

----------------------------------------------------------------------
    Chandra Seetharaman               | Be careful what you choose....
              - sekharan@us.ibm.com   |      .......you may get it.
----------------------------------------------------------------------

  reply	other threads:[~2008-01-25  2:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 18:25 Multipath Usage Guide available at LVM wiki page Chandra Seetharaman
2008-01-24 18:33 ` Pradipmaya Maharana
2008-01-24 22:21   ` Chandra Seetharaman
2008-01-25  2:14     ` malahal
2008-01-25  2:32       ` Chandra Seetharaman [this message]
2008-01-25  8:44         ` root

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=1201228340.2634.43.camel@linuxchandra \
    --to=sekharan@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.