From: Oliver Rath <oliver@greenunit.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Strange behaviour with thinpool and stripes
Date: Tue, 12 Jun 2018 13:08:38 +0200 [thread overview]
Message-ID: <fe22cc78-b2ad-535e-7e4b-2e0e308e726f@greenunit.de> (raw)
Hi List,
Im creating some Thinpool here, but
# lvcreate -i 2 -I 1024 -c 4096 --type thin --thinpool dmivg/winthinpool
dmivg -V 3500G /dev/sde1 /dev/sdf1
Command does not accept option: --stripes 2.
Command does not accept option: --stripesize 1024.
doesnt work, but
# lvcreate -i 2 -I 1024 -c 4096 -L10G -T dmivg/pool -V 3500G --name
winthinpool
WARNING: Sum of all thin volume sizes (3,42 TiB) exceeds the size of
thin pool dmivg/pool (10,00 GiB)!
For thin pool auto extension activation/thin_pool_autoextend_threshold
should be below 100.
Logical volume "winthinpool" created.
does. Whats the difference between them?
My actual build:
# lvcreate --version
LVM version: 2.02.172(2)-git (2017-05-03)
Library version: 1.02.141-git (2017-05-03)
Driver version: 4.35.0
Configuration: ./configure --enable-lvmetad --enable-lvmpolld
--enable-udev_sync --enable-udev_rules --enable-applib --enable-cmdlib
--enable-python2_bindings
Tfh!
Oliver
reply other threads:[~2018-06-12 11:08 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=fe22cc78-b2ad-535e-7e4b-2e0e308e726f@greenunit.de \
--to=oliver@greenunit.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).