[linux-lvm] Can't work normally after attaching disk volumes originally in a VG on another machine

Zdenek Kabelac zkabelac at redhat.com
Tue Mar 27 08:32:45 UTC 2018

Dne 27.3.2018 v 07:55 Gang He napsal(a):
> Hi Fran,
>> 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?
> I just reproduced a problem from the customer, since they did virtual disk migration from one virtual machine  to another one.
> According to your comments, this does not look like a LVM code problem,
> the problem can be considered as LVM administer misoperation?
> Thanks
> Gang

Ahh, so welcome Eric's replacement  :)

Yes - this use scenario was improper usage of lvm2 - and lvm2 has cached the 
user before he could ruing his data any further...



More information about the linux-lvm mailing list