[linux-lvm] Can't work normally after attaching disk volumes originally in a VG on another machine
franchu.garcia at gmail.com
Mon Mar 26 10:23:40 UTC 2018
On 26 March 2018 at 08:04, Gang He <ghe at suse.com> wrote:
> 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...
More information about the linux-lvm