From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Eric Ren <renzhengeek@gmail.com>
Subject: Re: [linux-lvm] Question about thin-pool/thin LV with stripes
Date: Fri, 25 Jan 2019 22:53:46 +0100 [thread overview]
Message-ID: <3d9fcd41-46df-aa71-7be9-f2258b7598e5@gmail.com> (raw)
In-Reply-To: <CAKM4Aezaxa-mFDbyq2uDvZZUM2xgi6GyGAHoQaeWnUn9JExcFw@mail.gmail.com>
Dne 24. 01. 19 v 16:06 Eric Ren napsal(a):
> Hi,
>
> 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?
>
>
> In our use scenario, we want to use DM thinp for a lot of containers as
> rootfs. The container use heavy on snapshots,
> so above 4K thin/snapshots LVs may share the thin pool concurrently.
>
> This may make the space fragmented. So, another concern is, will using striped
> thinp make
> fragmentation much more worse?
Hi
When 'stripe_size' is the 'right size' - striped device should appear faster,
but telling you what's the best size is some sort of 'black magic' :)
Basically - strip size should match boundaries of thin-pool chunk sizes.
i.e. for thin-pool with 128K chunksize - and 2 disks -
I'd assume best result you should get with 64K stripesize (so 2 disks will
make it 128K stripe) - but it depends on number of hw aspects.
So you will need to benchmark it.
Zdenek
next prev parent reply other threads:[~2019-01-25 21:53 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 [this message]
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:
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=3d9fcd41-46df-aa71-7be9-f2258b7598e5@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=renzhengeek@gmail.com \
/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
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).