Bug#474217: initramfs-tools: /etc/lvm.conf needed in initrd

[Bastian Blank]

tags 474217 moreinfo
thanks

On Fri, Apr 04, 2008 at 03:00:20PM +0200, Manon Goo wrote:
> >while creating an initrd the /etc/lvm.conf is not copied into the initrd,
> >this can result in a pretty ugly behaviours as the initrd will activate
> >all VG/LV it can find.

No, it tries to only activate the needed vg. Please show more about your
setup.

> >                       For example if you boot from SAN all LUNs will
> >show up in the initrd, including those which may be part of a cluster and
> >should not be activated (yet),

clustered vgs are marked and will never be activated until a functional
cluster is detected (or forced).

> >                                                           The listed
> >reasons are just a few why you probably don't want to activate all LVs,
> >and why you usually configure lvm in lvm.conf

What should happen if someone sets a cluster locking lib in lvm.conf
which is not available in the initramfs?

> >                                                ignoring this file can
> >result in a severe loss of data.

No, it does not. Activation does not write to the disks.

Bastian

-- 
Mind your own business, Spock.  I'm sick of your halfbreed interference.