From: David Teigland <teigland@redhat.com>
To: Neutron Sharc <neutronsharc@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] vgcreate failed when using iscsi + dm-multipath + lvm
Date: Tue, 14 Mar 2017 09:04:33 -0500 [thread overview]
Message-ID: <20170314140432.GB4723@redhat.com> (raw)
In-Reply-To: <CAB-bdyTrKbjREU_vRAHiLQvWBh=rt8Mh45CZ0_-3BsHKSkz_Nw@mail.gmail.com>
On Mon, Mar 13, 2017 at 06:12:06PM -0700, Neutron Sharc wrote:
> error 1:
> Physical volume '/dev/mapper/360000000557b690283509c3709c4fc0b' is
> already in volume group 'vol8',
> Unable to add physical volume
> '/dev/mapper/360000000557b690283509c3709c4fc0b' to volume group
> 'vol14'.
>
> error 2:
> Found duplicate PV W9rMQ0GuoNw9rnzK8x47OVEY044A2mgT: using
> /dev/mapper/360000000a1d91e849f66dd53a61d8fa9
> not /dev/mapper/360000000e2ddd2a9380e9159902d9f73, Using duplicate
> PV /dev/mapper/360000000a1d91e849f66dd53a61d8fa9 without holders,
> replacing /dev/mapper/360000000e2ddd2a9380e9159902d9f73,
>
> error 3:
> Can't open /dev/mapper/360000000e2ddd2a9380e9159902d9f73 exclusively.
> Mounted filesystem?
> Unable to add physical volume
> '/dev/mapper/360000000e2ddd2a9380e9159902d9f73' to volume group
> 'vol2'.
Fairly common problem, lvm needs to see only the multipath device and not
the components. Make sure lvm.conf has multipath_component_detection
enabled. There was also a recent related fix:
lvmetad: use udev to ignore multipath components during scan
next prev parent reply other threads:[~2017-03-14 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 1:12 [linux-lvm] vgcreate failed when using iscsi + dm-multipath + lvm Neutron Sharc
2017-03-14 14:04 ` David Teigland [this message]
2017-03-14 22:40 ` Neutron Sharc
2017-03-15 14:29 ` David Teigland
2017-03-15 20:04 ` Neutron Sharc
2017-03-15 1:08 ` pattonme
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=20170314140432.GB4723@redhat.com \
--to=teigland@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=neutronsharc@gmail.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).