From: Fran Garcia <fran@caosdigital.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Can't work normally after attaching disk volumes originally in a VG on another machine
Date: Mon, 26 Mar 2018 12:17:49 +0200 [thread overview]
Message-ID: <CAD+pdNfFB5mxqgVM6JB1Kz8e0cQjmkFe+AWWx3RSBmkSX-hJ1w@mail.gmail.com> (raw)
In-Reply-To: <5AB8FDE7020000F9000B19DD@prv-mh.provo.novell.com>
On 26 March 2018 at 08:04, Gang He <ghe@suse.com> wrote:
>> 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.
>
> It looks like each PV includes a copy meta data for VG, but if some PV has changed (e.g. removed, or moved to another VG),
> the remained PV should have a method to check the integrity when each startup (activated?), to avoid such inconsistent problem automatically.
Your workflow is strange. What are you trying to accomplish here?
Your steps in 5 should be:
vgreduce vg01 /dev/vdc /dev/vdc
pvremove /dev/vdc /dev/vdd
That way you ensure there's no leftover metadata in the PVs (specially
if you need to attach those disks to a different system)
Again a usecase to understand your workflow would be beneficial...
Cheers
Fran
next prev parent reply other threads:[~2018-03-26 10:18 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
2018-03-26 6:04 ` Gang He
2018-03-26 10:17 ` Fran Garcia [this message]
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=CAD+pdNfFB5mxqgVM6JB1Kz8e0cQjmkFe+AWWx3RSBmkSX-hJ1w@mail.gmail.com \
--to=fran@caosdigital.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).