linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Scott Moser <smoser@brickies.net>
Subject: Re: [linux-lvm] [PATCH] man: document that 2 times poolmetadatasize is allocated for lvmthin
Date: Wed, 28 Oct 2020 21:15:35 +0100	[thread overview]
Message-ID: <7971eb95-828e-37d5-b5fe-9bc67fccc29f@redhat.com> (raw)
In-Reply-To: <CAKxE60wD76RnJ=Zk690C5vajHjg3xuLANOoRih42VRQKrCriPw@mail.gmail.com>

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

  reply	other threads:[~2020-10-28 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 19:19 Scott Moser
2020-10-28 20:15 ` Zdenek Kabelac [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-20 18:25 Scott Moser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7971eb95-828e-37d5-b5fe-9bc67fccc29f@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=smoser@brickies.net \
    --subject='Re: [linux-lvm] [PATCH] man: document that 2 times poolmetadatasize is allocated for lvmthin' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).