2016-02-06 1:28 GMT+08:00 Zdenek Kabelac <zkabelac@redhat.com>: > But that's actually what described 'swap' is for. > > You 'replace/swap' existing metadata LV with some selected LV in VG. > > Then you activate this LV - and you may do whatever you need to do. > (so you have content of _tmeta LV accessible through your tmp_created_LV) I forget that we can use swapping to make _tmeta visible. The steps in this page are correct. http://www.spinics.net/lists/lvm/msg22629.html The only typo in this post is that we should use thin_repair instead of thin_restore. http://permalink.gmane.org/gmane.linux.lvm.general/14829 > lvm2 currently doesn't support activation of 'subLVs' as it makes > activation of the whole tree of LVs much more complicated (clvmd support > restrictions) > > So ATM we take only top-level LV lock in cluster (and yes - there is still > unresolved bug for thin-pool/thinLV - when user may 'try' to activate > different thin LVs from a single thin-pool on multiple nodes - so for now - > there is just one advice - don't do that - until we provide a fix for this. I didn't try clvm. Thanks for noticing. Ming-Hung Tsai _______________________________________________ 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/
