[linux-lvm] Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180

David Teigland teigland at redhat.com
Mon Oct 15 15:26:48 UTC 2018

On Sun, Oct 14, 2018 at 11:39:20PM -0600, Gang He wrote:
> >> [  147.371698] linux-472a dracut-initqueue[391]: Cannot activate LVs in VG 
> > vghome while PVs appear on duplicate devices.
> > 
> > Do these warnings only appear from "dracut-initqueue"?  Can you run and
> > send 'vgs -vvvv' from the command line?  If they don't appear from the
> > command line, then is "dracut-initqueue" using a different lvm.conf?
> > lvm.conf settings can effect this (filter, md_component_detection,
> > external_device_info_source).
> mdadm --detail --scan -vvv
> /dev/md/linux:0:
>            Version : 1.0

It has the old superblock version 1.0 located at the end of the device, so
lvm will not always see it.  (lvm will look for it when it's writing to
new devices to ensure it doesn't clobber an md component.)

(Also keep in mind that this md superblock is no longer recommended:

There are various ways to make lvm handle this:

- allow_changes_with_duplicate_pvs=1
- external_device_info_source="udev"
- reject sda2, sdb2 in lvm filter

> > It could be, since the new scanning changed how md detection works.  The
> > md superblock version effects how lvm detects this.  md superblock 1.0 (at
> > the end of the device) is not detected as easily as newer md versions
> > (1.1, 1.2) where the superblock is at the beginning.  Do you know which
> > this is?

More information about the linux-lvm mailing list