Bug 1899140 - [RFE] Allow creating pmspare volume on RAID
Summary: [RFE] Allow creating pmspare volume on RAID
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: 1079430
Blocks: 1119323
TreeView+ depends on / blocked
 
Reported: 2020-11-18 15:42 UTC by Zdenek Kabelac
Modified: 2024-04-27 05:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of: 1079430
Environment:
Last Closed:
Embargoed:
pm-rhel: lvm-technical-solution?
pm-rhel: lvm-test-coverage?


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.