linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Gang He" <ghe@suse.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
Date: Mon, 08 Oct 2018 04:23:27 -0600	[thread overview]
Message-ID: <5BBB301F020000F90003854E@prv1-mh.provo.novell.com> (raw)

Hello List

The system uses lvm based on raid1. 
It seems that the PV of the raid1 is found also on the single disks that build the raid1 device:
[  147.121725] linux-472a dracut-initqueue[391]: WARNING: PV qG1QRz-Ivm1-QVwq-uaHV-va9w-wwXh-lIIOhV on /dev/sda2 was already found on /dev/md1.
[  147.123427] linux-472a dracut-initqueue[391]: WARNING: PV qG1QRz-Ivm1-QVwq-uaHV-va9w-wwXh-lIIOhV on /dev/sdb2 was already found on /dev/md1.
[  147.369863] linux-472a dracut-initqueue[391]: WARNING: PV qG1QRz-Ivm1-QVwq-uaHV-va9w-wwXh-lIIOhV prefers device /dev/md1 because device size is correct.
[  147.370597] linux-472a dracut-initqueue[391]: WARNING: PV qG1QRz-Ivm1-QVwq-uaHV-va9w-wwXh-lIIOhV prefers device /dev/md1 because device size is correct.
[  147.371698] linux-472a dracut-initqueue[391]: Cannot activate LVs in VG vghome while PVs appear on duplicate devices.

This is a regression bug? since the user did not encounter this problem with lvm2 v2.02.177.


Thanks
Gang

             reply	other threads:[~2018-10-08 10:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 10:23 Gang He [this message]
2018-10-08 15:00 ` [linux-lvm] Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180 David Teigland
2018-10-15  5:39   ` Gang He
2018-10-15 15:26     ` David Teigland
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=5BBB301F020000F90003854E@prv1-mh.provo.novell.com \
    --to=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).