linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	mryan@lenovoemc.com
Subject: Re: [linux-lvm] resize of thin pool
Date: Thu, 27 Mar 2014 09:55:46 +0100	[thread overview]
Message-ID: <5333E792.9040709@gmail.com> (raw)
In-Reply-To: <E1D69AD765F9D841B8DE87D96DD21E450150B24B@AEMAILMBX02.lenovo.com>

Dne 27.3.2014 06:26, Michael Ryan napsal(a):
> Hi all.  Couple quick questions.
>
> 1.It is possible to resize (grow and shrink) the size of an active thin pool?

Only extension of thin pool is supported  (offline/online).
You cannot shrink the thin pool size.

(Theoretically you could relatively easily defragment chunks offline and 
update mapping, but this is not yet supported...)


> 2.What limitations exist on a thin volume with an external origin?  I
> understand the origin volume is effectively read-only, but can the thin volume
> be written to?  How about a snapshot of the thin volume with the external origin?
>

External origin has to be activated as a read-only volume.

The same external origin can be shared by many thin volumes even from 
different pool volumes. Of course you could then snapshot such thin volume as 
any other thin volume (i.e. chaining snapshot of snapshot of snapshot).
External origin can be still used as read-only normal LV and also it may be 
used as the origin for old-style traditional snapshot at the same time.

Current limitation is - you can't merge changes from your thin volume back
to your external origin (it's planed to add this feature in the future...)
Then there are some enforced limitation of the size alignments.

Zdenek

      reply	other threads:[~2014-03-27  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27  5:26 [linux-lvm] resize of thin pool Michael Ryan
2014-03-27  8:55 ` 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=5333E792.9040709@gmail.com \
    --to=zdenek.kabelac@gmail.com \
    --cc=linux-lvm@redhat.com \
    --cc=mryan@lenovoemc.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).