Bug 1427923 - [RFE] Provide a method to get the recommended thin pool metadata space size
Summary: [RFE] Provide a method to get the recommended thin pool metadata space size
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LVM Team
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 14:17 UTC by Vratislav Podzimek
Modified: 2023-08-10 15:40 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?

Attachments (Terms of Use)

Description Vratislav Podzimek 2017-03-01 14:17:40 UTC 
Description of problem:
IOW a DBus API for the (equivalent of the) thin_metadata_size tool.

Additional info:
Required for the related libblockdev-lvm-dbus functionality as implemented in https://github.com/rhinstaller/libblockdev/pull/168 (right now using the tool even in the DBus version of the plugin).
Comment 1 David Teigland 2017-03-01 16:39:30 UTC 
In lvmthin(7) we just tell people to use a 1GB thin metadata LV, and say that this will always be big enough.
Note You need to log in before you can comment on or make changes to this bug.