Bug 812734

Summary:	lvm should support to specify the metadata disk location when creating thin pool
Product:	[Fedora] Fedora	Reporter:	Xiaowei Li <xiaoli>
Component:	lvm2	Assignee:	Zdenek Kabelac <zkabelac>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17	CC:	agk, bmarzins, bmr, dwysocha, heinzm, jonathan, lvm-team, msnitzer, prajnoha, prockai, qcai, zkabelac
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-26 13:47:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	814732
Bug Blocks:

Description Xiaowei Li 2012-04-16 06:30:22 UTC

Description of problem:
currently lvcreate only supports to specify the metadata disk size when creating thin pool.
But it should also support to specify the physical disk used for metadata disk.

dmsetup can support to do this but cannot see it in lvcreate.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Zdenek Kabelac 2012-04-25 08:53:29 UTC

This problem will be resolved with generic lvconvert support, see Bug 814732 for progress.

Comment 2 Zdenek Kabelac 2012-10-11 10:12:25 UTC

Will be resolved with release of 2.02.98

Comment 3 Peter Rajnoha 2013-04-26 13:47:26 UTC

Fedora 17 is nearing its 'End of Life' in approx. two months from now, I don't expect any new updates for F17. This is fixed in F18 version of LVM2.