From: Oliver Rath <rath@mglug.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Different stripesize on thinpool/thinlv + config issue
Date: Tue, 9 May 2017 11:38:37 +0200 [thread overview]
Message-ID: <6608b02f-fcce-4bd3-61d2-7002eab4ffac@mglug.de> (raw)
Hi List,
using different stripesize for Thinpools result 64kb stripesize for ThinLVs.
---------- snip ------------------
root@w541:/home/oliver# lvcreate -L 20G --thin-pool levg/mythinpool
levg /dev/sda4 --stripes 1 --stripesize 1024
WARNING: Sum of all thin volume sizes (7,64 TiB) exceeds the size of
thin pools and the size of whole volume group (901,17 GiB)!
For thin pool auto extension activation/thin_pool_autoextend_threshold
should be below 100.
Logical volume "mythinpool" created.
root@w541:/home/oliver# lvcreate --name fixi -V 10G -T levg/mythinpool
Using default stripesize 64,00 KiB.
Logical volume "fixi" created.
---------- snap ------------------
Odd thing:
The striping-Options should prepare multiple disk in parallel for the
thinpool. But then the ThinLV says "using 64kb stripe", although 1024MB
is set for thinpool.
Additionally:
If I set in lvm.conf
----------------------------
metadata {
stripesize = 1024
}
----------------------------
it results in correct stripesize:
----------------------------
# lvcreate --name fixi3 -V 10G -T levg/mythinpool
Using default stripesize 1,00 MiB.
WARNING: Sum of all thin volume sizes (7,67 TiB) exceeds the size of
thin pools and the size of whole volume group (901,17 GiB)!
For thin pool auto extension activation/thin_pool_autoextend_threshold
should be below 100.
Logical volume "fixi3" created.
----------------------------
BUT
----------------------------
# lvcreate --stripesize 1024 --name fixi4 -V 10G -T levg/mythinpool
Command does not accept option: --stripesize 1024.
----------------------------
So setting stripesize in lvm.conf is allowed, in lvcreate
(thinpool-mode) not.
My used versions:
root@w541:/home/oliver# lvcreate --version
LVM version: 2.02.171(2)-git (2017-04-13)
Library version: 1.02.140-git (2017-04-13)
Driver version: 4.35.0
Configuration: ./configure --enable-lvmetad
root@w541:/home/oliver# thin_check --version
0.7.0-rc6
Whats wrong here?
Tfh!
Regards,
Oliver
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
reply other threads:[~2017-05-09 9:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6608b02f-fcce-4bd3-61d2-7002eab4ffac@mglug.de \
--to=rath@mglug.de \
--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).