Dne 27.3.2018 v 07:55 Gang He napsal(a):
Hi Fran,
On 26 March 2018 at 08:04, Gang He <ghe@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...
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
