Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1433146

Summary: fix raid down convert warning typo "losing"
Product: Red Hat Enterprise Linux 7 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: Heinz Mauelshagen <heinzm>
lvm2 sub component: Mirroring and RAID QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: unspecified CC: agk, heinzm, jbrassow, msnitzer, prajnoha, prockai, zkabelac
Version: 7.4   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.170-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 21:49:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2017-03-16 22:58:06 UTC 
Description of problem:
This behavior changed in just the latest lvm nightly build, there's now a warning needing confirmation (for just raid type).

lvm2-2.02.169-0.1251.el7    BUILT: Thu Mar 16 09:27:52 CDT 2017

# RAID1
[root@host-117 ~]# lvcreate -m 1 --type raid1 -L 100M VG
  Logical volume "lvol0" created.

[root@host-117 ~]# lvs -a -o +devices
  LV               VG    Attr       LSize   Cpy%Sync Devices
  lvol0            VG    rwi-a-r--- 100.00m 100.00   lvol0_rimage_0(0),lvol0_rimage_1(0)
  [lvol0_rimage_0] VG    iwi-aor--- 100.00m          /dev/sda1(1)
  [lvol0_rimage_1] VG    iwi-aor--- 100.00m          /dev/sdb1(1)
  [lvol0_rmeta_0]  VG    ewi-aor---   4.00m          /dev/sda1(0)
  [lvol0_rmeta_1]  VG    ewi-aor---   4.00m          /dev/sdb1(0)

[root@host-117 ~]# lvconvert -m 0 VG/lvol0
Are you sure you want to convert raid1 LV VG/lvol0 to type linear loosing all resilience? [y/n]: 

It did not change however for the mirror type:
# MIRROR
[root@host-117 ~]# lvcreate -m 1 --type mirror -L 100M VG
  Logical volume "lvol0" created.
[root@host-117 ~]# lvs -a -o +devices
  LV               VG    Attr       LSize   Log          Cpy%Sync Devices
  lvol0            VG    mwi-a-m--- 100.00m [lvol0_mlog] 100.00   lvol0_mimage_0(0),lvol0_mimage_1(0)
  [lvol0_mimage_0] VG    iwi-aom--- 100.00m                       /dev/sda1(0)
  [lvol0_mimage_1] VG    iwi-aom--- 100.00m                       /dev/sdb1(0)
  [lvol0_mlog]     VG    lwi-aom---   4.00m                       /dev/sdg1(0)

[root@host-117 ~]# lvconvert -m 0 VG/lvol0
  Logical volume VG/lvol0 converted.



This warning didn't exist at all in the prior lvm build:

lvm2-2.02.169-0.1248.el7    BUILT: Mon Feb 27 08:26:32 CST 2017

[root@host-087 ~]# lvcreate -m 1 --type raid1 -L 100M VG
  Logical volume "lvol0" created.

[root@host-087 ~]# lvs -a -o +devices
  LV               VG    Attr       LSize   Cpy%Sync Devices
  lvol0            VG    rwi-a-r--- 100.00m 100.00   lvol0_rimage_0(0),lvol0_rimage_1(0)
  [lvol0_rimage_0] VG    iwi-aor--- 100.00m          /dev/sda1(1)
  [lvol0_rimage_1] VG    iwi-aor--- 100.00m          /dev/sdb1(1)
  [lvol0_rmeta_0]  VG    ewi-aor---   4.00m          /dev/sda1(0)
  [lvol0_rmeta_1]  VG    ewi-aor---   4.00m          /dev/sdb1(0)

[root@host-087 ~]# lvconvert -m 0 VG/lvol0
  Logical volume VG/lvol0 successfully converted.


Version-Release number of selected component (if applicable):
3.10.0-609.el7.x86_64

lvm2-2.02.169-0.1251.el7    BUILT: Thu Mar 16 09:27:52 CDT 2017
lvm2-libs-2.02.169-0.1251.el7    BUILT: Thu Mar 16 09:27:52 CDT 2017
lvm2-cluster-2.02.169-0.1251.el7    BUILT: Thu Mar 16 09:27:52 CDT 2017
device-mapper-1.02.138-0.1251.el7    BUILT: Thu Mar 16 09:27:52 CDT 2017
device-mapper-libs-1.02.138-0.1251.el7    BUILT: Thu Mar 16 09:27:52 CDT 2017
device-mapper-event-1.02.138-0.1251.el7    BUILT: Thu Mar 16 09:27:52 CDT 2017
device-mapper-event-libs-1.02.138-0.1251.el7    BUILT: Thu Mar 16 09:27:52 CDT 2017
device-mapper-persistent-data-0.6.3-1.el7    BUILT: Fri Jul 22 05:29:13 CDT 2016
Comment 2 Corey Marthaler 2017-03-17 20:32:59 UTC 
splitmirrors as well:

[root@host-113 ~]# lvconvert --splitmirrors 1 --name new split_image/split_last_leg
Are you sure you want to split raid1 LV split_image/split_last_leg loosing all resilience? [y/n]:
Comment 3 Jonathan Earl Brassow 2017-04-12 15:39:28 UTC 
committed upstream:

commit ba12a2e81a319c22353c8e52bf29f55c924b2d9f
Author: Jonathan Brassow <jbrassow>
Date:   Wed Apr 12 10:28:19 2017 -0500

    Typo: change loose to lose

    loose (v): set free; release
    lose (v) : be deprived of or cease to have or retain

    We 'lose' redundancy or 'lose' meaning.
Comment 5 Corey Marthaler 2017-04-25 17:40:25 UTC 
Fix verified in the latest rpms.

3.10.0-651.el7.x86_64

lvm2-2.02.170-2.el7    BUILT: Thu Apr 13 14:37:43 CDT 2017
lvm2-libs-2.02.170-2.el7    BUILT: Thu Apr 13 14:37:43 CDT 2017
lvm2-cluster-2.02.170-2.el7    BUILT: Thu Apr 13 14:37:43 CDT 2017
device-mapper-1.02.139-2.el7    BUILT: Thu Apr 13 14:37:43 CDT 2017
device-mapper-libs-1.02.139-2.el7    BUILT: Thu Apr 13 14:37:43 CDT 2017
device-mapper-event-1.02.139-2.el7    BUILT: Thu Apr 13 14:37:43 CDT 2017
device-mapper-event-libs-1.02.139-2.el7    BUILT: Thu Apr 13 14:37:43 CDT 2017
device-mapper-persistent-data-0.7.0-0.1.rc6.el7    BUILT: Mon Mar 27 10:15:46 CDT 2017



[root@host-116 ~]# lvconvert -m 0 VG/lvol0
Are you sure you want to convert raid1 LV VG/lvol0 to type linear losing all resilience? [y/n]: y
  Logical volume VG/lvol0 successfully converted.

[root@host-116 ~]# lvconvert --splitmirrors 1 --name new1 VG/lvol1
Are you sure you want to split raid1 LV VG/lvol1 losing all resilience? [y/n]: y
Comment 6 errata-xmlrpc 2017-08-01 21:49:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2222