All of lore.kernel.org
 help / color / mirror / Atom feed
From: Malahal Naineni <malahal@us.ibm.com>
To: dm-devel@redhat.com
Subject: Re: oblem with lvm and multipath on fedora 13
Date: Sat, 28 Aug 2010 10:47:51 -0700	[thread overview]
Message-ID: <20100828174751.GA31397@us.ibm.com> (raw)
In-Reply-To: <C89D80D7.10732%brian.p.stamper@nasa.gov>

Stamper, Brian P. (ARC-D)[Logyx LLC] [brian.p.stamper@nasa.gov] wrote:
>    Here’s what I’ve found:
> 
>    If I vgchange the 2 affected VGs to inactive, multipath will pick up the
>    devices.  However, once I do that, I can’t seem to get the VGs reactivated
>    in such a way to make the volumes mountable.  I use vgchange –a y to make
>    the VG active, then do “vgscan —mknodes”.  That doesn’t seem to create the
>    devices in /dev, only in /dev/mapper, so I’ve tried issuing
>    /etc/init.d/udev-post reload, which does create the volumes in
>    /dev/<vg>/<lv>.  The issue is, it has no blkid.  And if I try to mount the
>    mapper device directly, mount doesn’t know what filesystem type it is.
>     I’m not an lvm pro, so it’s possible I’m missing a step or two, but in
>    the past when moving around snapshots of lvms, vgscan —mknodes has always
>    been sufficient.

The entries in /dev/mapper should work. If they don't work, other
entries don't work either. Based on the above information, can I assume
that you were able to mount such logical volumes without multipath (this
is very unusual, if true)? Inactivate affected VGs, run "multipath -F"
to delete multipath maps, and then activate your VGs. You should now be
where you were before and see if you can mount logical volumes that were
failing before (I doubt if they work though).


>    As for not having multipath in initrd, I have created an initrd image with
>    the following:
> 
>    mkinitrd /boot/initramfs-with-multipath.img 2.6.33.8-149.fc13.x86_64
>    --with=dm-multipath
> 
>    I then created a grub entry for it, booted off it, and no change in
>    behavior.  Is that what you had in mind?

RedHat mkinitrd scripts go to great lengths to not include multipath in
initrd unless you are currently using your 'root' on multipath! Most
likely it didn't include multipath. You can expand the initrd (it is a
compressed cpio archive, 'zcat initrd.img | cpio -icd' should extract
all the files) and see if multipath is included (look for multipath
in the extracted files). I would suggest you work on your first problem
(not able to mount stuff).

Thanks, Malahal.

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

  reply	other threads:[~2010-08-28 17:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 18:03 oblem with lvm and multipath on fedora 13 Stamper, Brian P. (ARC-D)[Logyx LLC]
2010-08-27 18:26 ` Malahal Naineni
2010-08-27 18:57   ` Stamper, Brian P. (ARC-D)[Logyx LLC]
2010-08-27 21:48   ` Stamper, Brian P. (ARC-D)[Logyx LLC]
2010-08-28 17:47     ` Malahal Naineni [this message]
2010-08-28 21:48       ` Stamper, Brian P. (ARC-D)[Logyx LLC]
2010-08-29 18:39         ` Malahal Naineni
2010-08-29 19:08           ` Stamper, Brian P. (ARC-D)[Logyx LLC]
2010-08-29 20:27             ` Malahal Naineni
2010-08-29 21:10               ` Stamper, Brian P. (ARC-D)[Logyx LLC]

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=20100828174751.GA31397@us.ibm.com \
    --to=malahal@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.