From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Request for Feature: Disk space usage by a LVM snapshot
Date: Tue, 24 Nov 2015 12:20:13 +0100 [thread overview]
Message-ID: <565447ED.4010808@redhat.com> (raw)
In-Reply-To: <CAO_L6qELj-F7Z3-MqM=_mhwmTnHEA1ZYe=Cc72cRGNCZ=h3K4A@mail.gmail.com>
Dne 23.11.2015 v 17:47 shankha napsal(a):
> Hi,
>
> Goal: We are trying to calculate actual disk usage of LVM Snapshots
> created from a thin logical volume.
>
> Method:
> Currently we use thin_dump to dump metadata information of all the LVM
> snapshots and logical volumes.
>
> Check what are the blocks unique to the snapshot and that gives you
> the size of the snapshot.
>
> The problem is while one is dumping data on the snapshot the metadata
> information which you get from thin dump is incorrect. That is what I noticed.
> Sometimes the tool will fail and it will ask you to repair your lvm metadata.
>
> ---
> Is there a way we can have a separate tool which will give us the disk
> usage of a LVM Snapshot.
>
Hi
Your most obvious bug here is - you try to use metadata from 'active'
thin-pool which you cannot (i.e. accessing /dev/mapper/vg-pool-tmeta -
which really IS private volume)
For now you need to take metadata snapshot (via dmsetup message - see kernel
target doc) as LVM2 doesn't yet expose this to user.
And in fact you should open "RFE" BZ entry to enhance thin tools to provide
you this needed info - since doing that on your own is just time waste,
as tools may easily calc this for you....
Zdenek
prev parent reply other threads:[~2015-11-24 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 16:47 [linux-lvm] Request for Feature: Disk space usage by a LVM snapshot shankha
2015-11-24 11:20 ` 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=565447ED.4010808@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).