From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Andres Toomsalu <andres@active.ee>
Subject: Re: [linux-lvm] strange usage stats for thin LV
Date: Fri, 02 Nov 2012 11:37:20 +0100 [thread overview]
Message-ID: <5093A260.8000906@redhat.com> (raw)
In-Reply-To: <73698D91-B8D4-4F52-ABF3-54542ACB0690@active.ee>
Dne 31.10.2012 01:04, Andres Toomsalu napsal(a):
> Hi,
>
> I'm a bit puzzled with some thin LV usage stats - hope that someone can shed a light on this.
> lvs shows that thin_backup LV is 94% used - but df shows only 16% - where comes the difference?
>
> lvs -a -o+metadata_percent
> LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert Meta%
> pool VolGroupL0 twi-a-tz 1,95t 35,17 2,79
> [pool_tdata] VolGroupL0 Twi-aot- 1,95t
> [pool_tmeta] VolGroupL0 ewi-aot- 14,00g
> root VolGroupL0 -wi-ao-- 10,00g
> swap VolGroupL0 -wi-ao-- 16,00g
> thin_backup VolGroupL0 Vwi-aotz 600,00g pool 94,51
> thin_storage VolGroupL0 Vwi-aotz 600,00g pool 20,98
>
>
> df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/VolGroupL0-root
> 9,9G 1,3G 8,1G 14% /
> tmpfs 16G 0 16G 0% /dev/shm
> /dev/sda1 1008M 122M 835M 13% /boot
> /dev/mapper/VolGroupL0-thin_storage
> 591G 39G 523G 7% /storage
> /dev/mapper/VolGroupL0-thin_backup
> 591G 90G 472G 16% /backup
>
> Thanks in advance,
>
As Stuart posted values are not related closely together.
But there are few things which are visible:
~35% tells you the number of used space in the pool - around ~700GB
~3% metadata takes - ~400MB
thin_backup has provisioned ~95% -> ~570GB
thin_storage ~21% -> ~130GB
which seem to match approximately number of used blocks from the pool
(~570 + ~130 = ~700)
===
Now to interpret your 'df' stats:
thin_storage uses 39GB stored in provisioned 130GB
thin_backup uses 90GB stored in provisioned 570GB
and there could be multi reasons for this:
- usage of large chunksize - and filesystem spreads a lot of data though the
device - either for it's internal maintenance, or a lot of files are located
across whole provisioned space.
- You have delete lots of files - and have not used discard for deleted areas
(i.e. for ext4 there is 'fstrim' command which will discard them)
So here you need to provide more information which filesystem is in use,
and what was the overall usage for your devices. And also are you using
discard support or not ?
What is the kernel version in use?
(It's always worth to use latest version of lvm2 - since there was improved
discard support configurability.
Zdenek
next prev parent reply other threads:[~2012-11-02 10:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 0:04 [linux-lvm] strange usage stats for thin LV Andres Toomsalu
2012-10-31 0:30 ` Stuart D Gathman
2012-11-02 10:37 ` Zdenek Kabelac [this message]
2012-11-02 10:46 ` Andres Toomsalu
2012-11-02 11:20 ` Zdenek Kabelac
2012-11-02 11:29 ` Andres Toomsalu
2012-11-07 22:03 ` Andres Toomsalu
2012-11-07 22:24 ` Mike Snitzer
2012-11-19 14:47 ` Lukáš Czerner
2012-11-07 22:03 ` Andres Toomsalu
-- strict thread matches above, loose matches on Subject: below --
2012-11-09 14:19 Vitaly Yakovenko
2012-11-11 8:22 ` Vitaly Yakovenko
2012-11-14 11:22 ` Andres Toomsalu
2012-11-19 14:33 ` Vitaly Yakovenko
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=5093A260.8000906@redhat.com \
--to=zkabelac@redhat.com \
--cc=andres@active.ee \
--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).