From: Xen <list@xenhideout.nl>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Can't work normally after attaching disk volumes originally in a VG on another machine
Date: Fri, 23 Mar 2018 10:04:29 +0100 [thread overview]
Message-ID: <229d22d1217a7fa96874df0fb6d53e0c@xenhideout.nl> (raw)
In-Reply-To: <5AB52B8D020000F9000B14B9@prv-mh.provo.novell.com>
Gang He schreef op 23-03-2018 9:30:
> 6) attach disk2 to VM2(tb0307-nd2), the vg on VM2 looks abnormal.
> tb0307-nd2:~ # pvs
> WARNING: Device for PV JJOL4H-kc0j-jyTD-LDwl-71FZ-dHKM-YoFtNV not
> found or rejected by a filter.
> PV VG Fmt Attr PSize PFree
> /dev/vdc vg2 lvm2 a-- 20.00g 20.00g
> /dev/vdd vg1 lvm2 a-- 20.00g 20.00g
> [unknown] vg1 lvm2 a-m 20.00g 20.00g
This is normal because /dev/vdd contains metadata for vg1 which includes
now missing disk /dev/vdc .... as the PV is no longer the same.
> tb0307-nd2:~ # vgs
> WARNING: Device for PV JJOL4H-kc0j-jyTD-LDwl-71FZ-dHKM-YoFtNV not
> found or rejected by a filter.
> VG #PV #LV #SN Attr VSize VFree
> vg1 2 0 0 wz-pn- 39.99g 39.99g
> vg2 1 0 0 wz--n- 20.00g 20.00g
This is normal because you haven't removed /dev/vdc from vg1 on
/dev/vdd, since it was detached while you operated on its vg.
> 7) reboot VM2, the result looks worse (vdc disk belongs to two vg).
> tb0307-nd2:/mnt/shared # pvs
> PV VG Fmt Attr PSize PFree
> /dev/vdc vg1 lvm2 a-- 20.00g 0
> /dev/vdc vg2 lvm2 a-- 20.00g 10.00g
> /dev/vdd vg1 lvm2 a-- 20.00g 9.99g
When you removed vdd when it was not attached, the VG1 metadata on vdd
was not altered. The metadata resides on both disks, so you had
inconsistent metadata between both disks because you operated on the
shared volume group while one device was missing.
You also did not recreate PV on /dev/vdc so it has the same UUID as when
it was part of VG1, this is why VG1 when VDD is booted will still try to
include /dev/vdc because it was never removed from the volume group on
VDD.
So the state of affairs is:
/dev/vdc contains volume group info for VG2 and includes only /dev/vdc
/dev/vdd contains volume group info for VG1, and includes both /dev/vdc
and /dev/vdd by UUID for its PV, however, it is a bug that it should
include /dev/vdc even though the VG UUID is now different (and the name
as well).
Regardless, from vdd's perspective /dev/vdc is still part of VG1.
next prev parent reply other threads:[~2018-03-23 9:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 8:30 [linux-lvm] Can't work normally after attaching disk volumes originally in a VG on another machine Gang He
2018-03-23 9:04 ` Xen [this message]
2018-03-26 6:04 ` Gang He
2018-03-26 10:17 ` Fran Garcia
2018-03-26 10:23 ` Fran Garcia
2018-03-27 5:55 ` Gang He
2018-03-27 8:32 ` Zdenek Kabelac
2018-03-28 2:09 ` Gang He
2018-03-27 9:12 ` Xen
2018-03-27 10:22 ` Zdenek Kabelac
2018-03-27 10:27 ` Xen
2018-03-27 22:17 ` Zdenek Kabelac
2018-03-28 10:08 ` Xen
2018-03-26 10:46 ` Zdenek Kabelac
2018-05-18 4:56 ` Gang He
2018-03-26 11:33 ` Xen
2018-10-16 20:59 ` [linux-lvm] [lvm-devel] " Nir Soffer
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=229d22d1217a7fa96874df0fb6d53e0c@xenhideout.nl \
--to=list@xenhideout.nl \
--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).