From: David Teigland <teigland@redhat.com>
To: Gang He <ghe@suse.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
Date: Mon, 15 Oct 2018 10:26:48 -0500 [thread overview]
Message-ID: <20181015152648.GB29274@redhat.com> (raw)
In-Reply-To: <5BC42808020000F90003A3E5@prv1-mh.provo.novell.com>
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:
raid.wiki.kernel.org/index.php/RAID_superblock_formats)
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?
next prev parent reply other threads:[~2018-10-15 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 10:23 [linux-lvm] Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180 Gang He
2018-10-08 15:00 ` David Teigland
2018-10-15 5:39 ` Gang He
2018-10-15 15:26 ` David Teigland [this message]
2018-10-17 5:16 ` Gang He
2018-10-17 14:10 ` David Teigland
2018-10-17 18:42 ` David Teigland
2018-10-18 8:51 ` Gang He
2018-10-18 16:01 ` David Teigland
2018-10-18 17:59 ` David Teigland
2018-10-19 5:42 ` Gang He
2018-10-23 2:19 ` Gang He
2018-10-23 15:04 ` David Teigland
[not found] ` <59EBFA5B020000E767ECE9F9@prv1-mh.provo.novell.com>
2018-10-24 2:23 ` Gang He
2018-10-24 14:47 ` David Teigland
2018-10-17 17:11 ` Sven Eschenberg
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=20181015152648.GB29274@redhat.com \
--to=teigland@redhat.com \
--cc=ghe@suse.com \
--cc=linux-lvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).