Bug 1427923

Summary:	[RFE] Provide a method to get the recommended thin pool metadata space size
Product:	[Community] LVM and device-mapper	Reporter:	Vratislav Podzimek <vpodzime>
Component:	lvm2	Assignee:	LVM Team <lvm-team>
lvm2 sub component:	lvmdbusd	QA Contact:	cluster-qe <cluster-qe>
Status:	NEW ---	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	agk, heinzm, jbrassow, msnitzer, pasik, prajnoha, tasleson, teigland, zkabelac
Version:	unspecified	Flags:	rule-engine: lvm-technical-solution? rule-engine: lvm-test-coverage?
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.