Bug 1899140

Summary: [RFE] Allow creating pmspare volume on RAID
Product: [Community] LVM and device-mapper Reporter: Zdenek Kabelac <zkabelac>
Component: lvm2Assignee: LVM Team <lvm-team>
lvm2 sub component: Command-line tools QA Contact: cluster-qe <cluster-qe>
Status: NEW --- Docs Contact:
Severity: unspecified    
Priority: unspecified CC: agk, heinzm, jbrassow, mcsontos, prajnoha, thornber, zkabelac
Version: unspecifiedKeywords: FutureFeature
Target Milestone: ---Flags: pm-rhel: lvm-technical-solution?
pm-rhel: lvm-test-coverage?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: 1079430 Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1079430    
Bug Blocks: 1119323    

Description Zdenek Kabelac 2020-11-18 15:42:11 UTC
At the moment pmspare is created as a linear volume. There is no way how to make it redundant.

lvcreate and lvrename fails with:

    Names including "_pmspare" are reserved. Please choose a different LV name.

I assume we may eventally support 'lvconvert -m+X'  for _pmspare.

On the other hand _pmspare is 'last resource' weapon not even normally used - it's reserved space for recovery operation when everything else fails thus it should not really matter which type is that.

What user should be always able to make is to 'pvmove & lvconvert' real _tmeta & _cmeta volumes.

_pmspare does not normally hold any data so it's rather lost space to use raid for such volume - lvm2 never automatically 'deletes' old metadata volume,
so there should be always original version on raid.