From: Eric Ren <renzhengeek@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Question about thin-pool/thin LV with stripes
Date: Wed, 23 Jan 2019 21:40:05 +0800 [thread overview]
Message-ID: <CAKM4Aexk-=PBRMCUvXwzHxXzWCbYL22dSo+uHFXaasVCVuKddA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]
Hello,
I created thin LVs with 2 stripes on two PVs as follows:
```
lvcreate --yes --zero=n --type=thin-pool --name=mythinpool
--extents=90%FREE --chunksize=512K --poolmetadatasize=1G --stripes=2
--stripesize=4K vg0
...
# lvs -o+stripes -a
LV VG Attr LSize Pool Origin Data%
Meta% Move Log Cpy%Sync Convert #Str
RootVolume vg0 Vwi-a-t--- 10.00g mythinpool 1.36
0
[lvol0_pmspare] vg0 ewi------- 2.00g
1
mythinpool vg0 twi-aot--- <175.77g 0.08 0.79
1
[mythinpool_tdata] vg0 Twi-ao---- <175.77g
2
[mythinpool_tmeta] vg0 ewi-ao---- 2.00g
1
# dmsetup table
vg0-mythinpool: 0 368607232 linear 252:2 0
vg0-RootVolume: 0 20971520 thin 252:2 1
vg0-mythinpool-tpool: 0 368607232 thin-pool 252:0 252:1 1024 71993 1
skip_block_zeroing
vg0-mythinpool_tdata: 0 368607232 striped 2 8 254:16 4458496 254:32 264192
vg0-mythinpool_tmeta: 0 4194304 linear 254:16 188762112
```
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?
Besides, is there anything I should take care of to extend the VG/thin-pool
with *striped thin-LV*
when out of space?
Any suggestion would be very appreciated, thanks in advance!
Regards,
Eric Ren
[-- Attachment #2: Type: text/html, Size: 2452 bytes --]
next reply other threads:[~2019-01-23 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 13:40 Eric Ren [this message]
2019-01-24 14:54 ` [linux-lvm] Question about thin-pool/thin LV with stripes 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
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='CAKM4Aexk-=PBRMCUvXwzHxXzWCbYL22dSo+uHFXaasVCVuKddA@mail.gmail.com' \
--to=renzhengeek@gmail.com \
--cc=linux-lvm@redhat.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).