Bug 1427492 - [RFE] Handle spare volume creation more efficiently
Summary: [RFE] Handle spare volume creation more efficiently
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.169
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LVM Team
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-28 11:26 UTC by Zdenek Kabelac
Modified: 2023-08-10 15:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?


Attachments (Terms of Use)

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:


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