From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Questions about thin pools and segment properties
Date: Thu, 29 Nov 2012 11:39:01 +0100 [thread overview]
Message-ID: <50B73B45.6040104@redhat.com> (raw)
In-Reply-To: <2726839.KTFC4Ya9jJ@laptop>
Dne 29.11.2012 04:07, ben napsal(a):
> If I start with a pool like this:
>
> lvs --all --segments -o +chunksize,discards
> LV VG Attr #Str Type SSize Chunk Discards
> pool1 vg1 twi-a-tz- 1 thin-pool 100.00m 64.00k passdown
> [pool1_tdata] vg1 Twi-aot-- 1 linear 50.00m 0
> [pool1_tdata] vg1 Twi-aot-- 1 linear 50.00m 0
> [pool1_tmeta] vg1 ewi-aot-- 1 linear 2.00m 0
>
> My first question is if I look at "pool1" with liblvm2pp will
> there ever be more than one segment? I know "pool1_tdata"
For now yes - thin pool volume should (and internally must have)
only 1 segment.
> can have more but it looks like "pool1" is just one.
> My second question is if discards and chunksize are segment
> properties, can a pool have more than one setting of either?
LV is container of segments - segment has its type - and they have their
properties. The problem is there is not very clear distinction/definition
what is actually property of LV and what is property of lvsegment and a lot
of segment properties have landed historically as LV property.
There is some black magic internally to handle things properly.
But lvm2 will not allow you to create i.e. linear volume with thin pool
segment inside (unless there is a bug).
My proposal here would be - to probably auto magically check for
segment properties in the first LV segment if they are queried via
lv property call. (Agk ?) - that would probably made the live easier.
Zdenek
prev parent reply other threads:[~2012-11-29 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 3:07 [linux-lvm] Questions about thin pools and segment properties ben
2012-11-29 10:39 ` Zdenek Kabelac [this message]
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=50B73B45.6040104@redhat.com \
--to=zkabelac@redhat.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).