From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Howto get real size of thinpool-snap?
Date: Wed, 15 Jul 2015 19:51:19 +0200 [thread overview]
Message-ID: <55A69D97.8040308@gmail.com> (raw)
In-Reply-To: <55A6565A.6060307@mglug.de>
Dne 15.7.2015 v 14:47 Oliver Rath napsal(a):
> Hi list,
>
> if I create a snapshot of a volume in a thinpool, first only metadata
> need space. Later, through copy-on-write, the real needed size grows. Is
> it possible to get this size?
>
When you access thin-pool kernel metadata - you could write your own tool
to parse i.e. thin_dump output and calc all info you want.
There is no 'runtime' info (since it would be quite expensive to maintain such
info all the time).
Currently lvm2 doesn't support 'life' access to running thin-pool,
but you may eventually use dmsetup message to take snapshot and access this
info runtime (since kernel target supports this).
Zdenek
prev parent reply other threads:[~2015-07-15 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 12:47 [linux-lvm] Howto get real size of thinpool-snap? Oliver Rath
2015-07-15 17:51 ` 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=55A69D97.8040308@gmail.com \
--to=zdenek.kabelac@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).