Description of problem: Enhance thin tools support to calculate actual disk usage of thin logical volumes and LVM Snapshots created from a thin logical volume. Expected results: The actual disk usage of each lvm snapshot and lvm thin volume. If possible the capability to ask for the size based on thin id/name of the snapshot or thin logical volume. Thanks
In case you're requesting the metadata footage, see tool thin_metadata_size
The bug here tries to learn the 'space' occupied by individual LV. It has some 'shared' mapppings And some 'exlusive' mappings. Initially we should provide some 'script' to calc these 2 values. Later those could be built-in into e.g. thin_dump tool. Let's think about how lvm2 could make it easier for user.
Could you please let me know if there are any plans for this RFE. Thanks
(In reply to Gudge from comment #3) > Could you please let me know if there are any plans for this RFE. The latest device-mapper-persistent-data package should include the new 'thin_ls' utility. But I'll defer to Joe and/or Peter to say definitively.
Yes, we have thin_ls in device-mapper-persistent-data package since device-mapper-persistent-data-0.6.0-1 (20th January).
But still, we're planning to display this info in LVM command directly (this is RFE for lvm2).
thin_ls is tool from 'd-m-p-d' set of tools and as such it requires access to 'stable' version of kernel metadata (aka _tmeta) device (i.e. very similar to thin_dump) For active thin-pool - that means creating a kernel metadata snapshot and access this content. For inactive thin-pool - user needs to active (component activation) _tmeta volume and use this device to obtain info. There is 'native' support for this tool inside lvm2.