Bug 1427492

Summary:	[RFE] Handle spare volume creation more efficiently
Product:	[Community] LVM and device-mapper	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	LVM Team <lvm-team>
lvm2 sub component:	Cache Logical Volumes	QA Contact:	cluster-qe <cluster-qe>
Status:	NEW ---	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	agk, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac
Version:	2.02.169	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 Zdenek Kabelac 2017-02-28 11:26:52 UTC

Description of problem:

Current lvm2 command handles '_pmspare' allocation as 'standalone' and allocation and clearing process with multiple metadata write steps.

The more efficient way likely seems to join 'creating and activation' of metadata volume (for cache & thinpool) into a single step  - activating 2 LVs in single step - this should also simplify allocation logic and allow proper revert of both steps at once.

Similar logic should be then applied to resize of metadata volume and _pmspare.


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

How reproducible:


Steps to Reproduce:
1. lvcreate -L1 -T vg/tpool
2.
3.

Actual results:
Multiple separate activation and metadata writes to make thin-pool metadata volumes and _pmspare

Expected results:
Should be reduce to a single activation of both such LVs.


Additional info: