archive mirror
 help / color / mirror / Atom feed
From: Eric Ren <>
Subject: Re: [linux-lvm] Question about thin-pool/thin LV with stripes
Date: Thu, 24 Jan 2019 22:54:32 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]


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?

My main concern here is, if the metadata LV use stripped target, can
thin_check/thin_repair tools work fine?

> Besides, is there anything I should take care of to extend the
> VG/thin-pool with *striped thin-LV*
> when out of space?

In this case, I should always vgextend the VG with 2 PVs, because thin pool
will find the half-of-extending-size
of free space on 2 seperate PVs for striping. If just adding one PV, the
free space in VG cannot be used
to extend the 2-striped thin-pool.


[-- Attachment #2: Type: text/html, Size: 1743 bytes --]

  reply	other threads:[~2019-01-24 14:54 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 [this message]
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

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 \
    --in-reply-to='' \ \ \

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