Re: [PATCH] man: document that 2 times poolmetadatasize is allocated for lvmthin

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dne 20. 10. 20 v 21:19 Scott Moser napsal(a):
diff --git a/man/lvmthin.7_main b/man/lvmthin.7_main
index ce2343183..e21e516c9 100644
--- a/man/lvmthin.7_main
+++ b/man/lvmthin.7_main
@@ -1101,6 +1101,11 @@ specified with the --poolmetadatasize option.
When this option is not
  given, LVM automatically chooses a size based on the data size and chunk
  size.

+The space allocated by creation of a thinpool will include
+a spare metadata LV by default (see "Spare metadata LV").  As a result,
+the VG must have enough space for the --size option plus twice
+the specified (or calculated) --poolmetadata value.



Hi

The patch is unfortunately not really precise.

This applies only when you allocate first pool type volume in a VG.

IMHO better is to refer directly into 'lvmthin' man page for closer detail
if user is interested.

Majority of users simply does not care about negligible size of metadata
volume, so the information is rather for very experienced users and
should be in some dedicated section for them.

Regards

Zdenek

_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/




[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux