Bug 1477374 - RAID upconversion looks like resync on older kernels
Summary: RAID upconversion looks like resync on older kernels
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.174
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: Heinz Mauelshagen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-01 22:40 UTC by Zdenek Kabelac
Modified: 2021-11-15 19:54 UTC (History)
7 users (show)

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

Attachments (Terms of Use)

Description Zdenek Kabelac 2017-08-01 22:40:25 UTC 
Description of problem:

When 'lvconvert -m+1  vg/lv' is used to upconvert LV to raid1 it looks like 'resync' with older kernels.

status reports  'aa  X/Y resync' and such operation is evauluated as
'extreactable' via function  _raid_allow_extraction().

So in such case it has lost the meaning of 'origin' and replica-leg
and user is allowed to 'remove'  1st. (origin) leg.

Observable on Fedora 19, RH6...

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


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