Bug 1477374 - RAID upconversion looks like resync on older kernels
RAID upconversion looks like resync on older kernels
Status: NEW
Product: LVM and device-mapper
Classification: Community
Component: lvm2 (Show other bugs)
2.02.174
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: LVM and device-mapper development team
cluster-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-01 18:40 EDT by Zdenek Kabelac
Modified: 2017-08-01 18:40 EDT (History)
6 users (show)

See Also:
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: ---
rule-engine: lvm‑technical‑solution?
rule-engine: lvm‑test‑coverage?


Attachments (Terms of Use)

  None (edit)
Description Zdenek Kabelac 2017-08-01 18:40:25 EDT
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.