[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [dm-devel] oblem with lvm and multipath on fedora 13

Stamper, Brian P. (ARC-D)[Logyx LLC] [brian p stamper nasa gov] wrote:
> Yes, it's chkconfig'ed on, and I bumped forward its start order to
> start up prior to lvm2-monitor, thinking lvm2-monitor (which does
> vgscan) might be part of the problem.

Don't change any default orders. That is not a proper fix even if it
works and you may break other things.

> >> [root testfs foo]# find . -print | grep -i multi
> >> ./lib/modules/
> >The dm-multipath.ko kernel module is present. It needs multipath command
> >calling from an initrd script (/init ???)
> I'm not positive that I'm sure what you're asking.  Do you mean the
> init.d script I reference above, or is there some other configuration
> change to call mulitpath from initrd?

What I was trying to say is that dm-multipath.ko is included in the
initrd image, but there are other things that need to be included in the
initrd image to make the multipath configuration work in the initrd. For
example, you need multipath.conf in the initrd image as well as some
script in the initrd image calling 'multipath' binary.

> I feel much better knowing that I can get back to a proper
> configuration manually, but any ideas about why this is happening on
> bootup? 

My best guess is that LVM gets configured in initrd and multipath is not
there until the active root FS. Your best bet would be to include
multipath in the initrd (I have no working instructions on how to build
initrd with multipath on recent RedHat distros).

You may be able to get around the problem by restricting LVM in the
initrd image by doing this:

1. Modify the filter in /etc/lvm.conf file to include only the root/swap
2. Make a new initrd image. Use this to boot now onwards
   Since your filter only includes root/swap paths, LVM won't find or
   configure logical volumes other than root and swap at initrd time!
3. Change the filter to what it should be (the distro default should be
4. Now reboot.

> FYI, I played around with filtering in lvm.conf in my first
> night of troubleshooting and tried filtering out all /dev/sd.* drives
> other than /dev/sda, but it seems like dracut was ignoring the lvm
> filters, despite the lvm.conf.  With the filter in place a pvscan
> would find no duplicates (and no sd.* devices) but on reboot dracut
> would find them all and report the dupes.

Did you make a new initrd after changing the lvm.conf file? Your initrd
will have a copy of lvm.conf file (it would be some old file unless you
made a new initrd image) and that would be used at boot up as you have
configured LVM in initrd.
> Thanks for your help so far Malahal.

You are welcome.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]