linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Gionatan Danti <g.danti@assyoma.it>
Cc: Ilia Zykov <mail@izyk.ru>
Subject: Re: [linux-lvm] Maximum address used by a virtual disk on a thin pool.
Date: Fri, 14 Jun 2019 10:54:56 +0200	[thread overview]
Message-ID: <8ed636be-e43f-d97b-e994-31ccb40c71a7@redhat.com> (raw)
In-Reply-To: <7ee5ada1a5dc5256064c475f3179c6ac@assyoma.it>

Dne 13. 06. 19 v 21:54 Gionatan Danti napsal(a):
> Il 13-06-2019 18:05 Ilia Zykov ha scritto:
>> Hello.
>> Tell me please, how can I get the maximum address used by a virtual disk
>> (disk created with -V VirtualSize). I have several large virtual disks,
>> but they use only a small part at the beginning of the disk. For example:
>>
>> # lvs
>> � LV�������� VG� Attr������ LSize�� Pool���� Origin Data%
>> � mylvm����� CVG Vwi-aot--- 100,00g fastheap������� 7,13
>>
>>
>> Please advise me how to determine from which address the virtual disk
>> did not allocate real disk space? And all the data read from addresses
>> greater than this address will be exactly zeros. Or maybe, how can I get
>> map of the used chunks of disk?
>>
>> Thanks.
> 
> Maybe thin_dump[1] can help you?
> Regards.
> 
> [1] https://linux.die.net/man/8/thin_dump

Hi

There is even better tool that can expose in 'great detail' ownership of
individual thin-pool chunks for each  thin volume - if that's what you
are looking for.  See  'man  thin_ls'

Regards

Zdenek

      reply	other threads:[~2019-06-14  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 16:05 [linux-lvm] Maximum address used by a virtual disk on a thin pool Ilia Zykov
2019-06-13 19:54 ` Gionatan Danti
2019-06-14  8:54   ` 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=8ed636be-e43f-d97b-e994-31ccb40c71a7@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=g.danti@assyoma.it \
    --cc=linux-lvm@redhat.com \
    --cc=mail@izyk.ru \
    /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).