On 10/06/2014 11:05 AM, Patrik Horník wrote:
Thank you very much, now I understand.
But apparently I dont understand exact function of " lvconvert
--thinpool vg/mypool --poolmetadata mytemplv" So it also copies
metadata from current metadata LV to mytemplv?
Nope, the metadata are copied by `thin_repair` step:
# thin_repair -i /dev/vg/mytemplv -o /dev/vg/mynewsizemeta
The lvconvert "only" swaps LVs.
-- Martian
Then what about "lvconvert --thinpool vg/mypool --poolmetadata
mynewsizemeta"? It does not do that because mynewsizemeta is smaller
than current metadata mytemplv or?
2014-10-06 10:57 GMT+02:00 Zdenek Kabelac <zkabelac@xxxxxxxxxx>:
Dne 6.10.2014 v 10:48 Patrik Horník napsal(a):
Thanks Zdenku. But you did not answer some of my questions, which I
need to know to decide... So is there a way I can create smaller spare
metadata LV? In mentioned manual steps what do I need mytemplv for and
why cant I use original pool metadata as input of thin_repair?
Spare volume is maintained to have the size at least as the biggest
pool metadata volume in VG.
There is no point to keep smaller reserved space.
We do not allow to activate 'subvolumes' - thus you cannot activate
just 'thin pool metadata' - that's why you need to swap _tmeta
out thin pool.
Zdenek
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
