linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
* [linux-lvm] [PATCH] man: document that 2 times poolmetadatasize is allocated for lvmthin
@ 2020-10-20 18:25 Scott Moser
  0 siblings, 0 replies; 3+ messages in thread
From: Scott Moser @ 2020-10-20 18:25 UTC (permalink / raw)
  To: linux-lvm

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.
+
 It can be hard to predict the amount of metadata space that will be
 needed, so it is recommended to start with a size of 1GiB which should be
 enough for all practical purposes.  A thin pool metadata LV can later be

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [linux-lvm] [PATCH] man: document that 2 times poolmetadatasize is allocated for lvmthin
  2020-10-20 19:19 Scott Moser
@ 2020-10-28 20:15 ` Zdenek Kabelac
  0 siblings, 0 replies; 3+ messages in thread
From: Zdenek Kabelac @ 2020-10-28 20:15 UTC (permalink / raw)
  To: LVM general discussion and development, Scott Moser

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [linux-lvm] [PATCH] man: document that 2 times poolmetadatasize is allocated for lvmthin
@ 2020-10-20 19:19 Scott Moser
  2020-10-28 20:15 ` Zdenek Kabelac
  0 siblings, 1 reply; 3+ messages in thread
From: Scott Moser @ 2020-10-20 19:19 UTC (permalink / raw)
  To: linux-lvm

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.
+
 It can be hard to predict the amount of metadata space that will be
 needed, so it is recommended to start with a size of 1GiB which should be
 enough for all practical purposes.  A thin pool metadata LV can later be

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-10-28 20:15 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-20 18:25 [linux-lvm] [PATCH] man: document that 2 times poolmetadatasize is allocated for lvmthin Scott Moser
2020-10-20 19:19 Scott Moser
2020-10-28 20:15 ` Zdenek Kabelac

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).