archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: LVM general discussion and development <>,
	Eric Ren <>
Subject: Re: [linux-lvm] Question about thin-pool/thin LV with stripes
Date: Fri, 25 Jan 2019 22:47:19 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 24. 01. 19 v 15:54 Eric Ren napsal(a):
> Hi,
>     As you can see, only "mythinpool_tdata" LV has 2 stripes. Is that OK?
>     If I want to benefit performance from stripes, will it works for me? Or,
>     should I create dataLV, metadata LV, thinpool and thin LV using
>     step-by-step way
>     and specify "--stripes 2" in every steps?
> With single command to create thin-pool, the metadata LV is not created with 
> striped
> target. Is this designed on purpose, or just the command doesn't handle this 
> case very
> well for now?


Yes this on purpose currently.

When you create 'thin-pool' - you are mostly specifying options for 'DATA' 
volume. The allocation of metadata is using 'internals' to pick the place
and other properties -  we can maybe introduce some policy option
to make metadata raid1 or striped or something like that.

ATM it's not so easy to do the best possible allocation - so
for skilled admin - it's always most 'secure' to build pool
from bricks - data LV + meta LV.

The automatic allocation will get enhanced over the time - but it's
always somewhere 'fuzzy' what is going to be the results.

Basically - what is 'unspecified' on command line and left for lvm2 to figure 
out - may change between releases - if we consider there is better solution.


      parent reply	other threads:[~2019-01-25 21:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 13:40 [linux-lvm] Question about thin-pool/thin LV with stripes Eric Ren
2019-01-24 14:54 ` Eric Ren
2019-01-24 15:06   ` Eric Ren
2019-01-25 21:53     ` Zdenek Kabelac
2019-01-26  3:36       ` Eric Ren
2019-01-25 21:47   ` Zdenek Kabelac [this message]

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:

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

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).