1283759 – raid10 conversion attempt with -m flag failure should be handled better

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 1283759 - raid10 conversion attempt with -m flag failure should be handled better

Summary: raid10 conversion attempt with -m flag failure should be handled better

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	lvm2
Sub Component:
Version:	7.2
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	low
Target Milestone:	rc
Target Release:	---
Assignee:	David Teigland
QA Contact:	cluster-qe@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2015-11-19 18:28 UTC by Corey Marthaler
Modified:	2021-09-03 12:38 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2020-12-15 07:38:38 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Corey Marthaler 2015-11-19 18:28:05 UTC

Description of problem:
[root@host-112 ~]# lvs
  LV     VG            Attr       LSize   Cpy%Sync Convert
  raid1  snapper_thinp rwi-a-r--- 100.00m 100.00          
  raid10 snapper_thinp rwi-a-r--- 104.00m 100.00          
  raid4  snapper_thinp rwi-a-r--- 104.00m 100.00          
  raid5  snapper_thinp rwi-a-r--- 104.00m 100.00          
  raid6  snapper_thinp rwi-a-r--- 108.00m 100.00          

# no -m flag
[root@host-112 ~]# for i in 1 10 4 5 6; do lvconvert --type raid1 snapper_thinp/raid$i; done
  Converting the segment type for snapper_thinp/raid1 from raid1 to raid1 is not yet supported.
  Converting the segment type for snapper_thinp/raid10 from raid10 to raid1 is not yet supported.
  Converting the segment type for snapper_thinp/raid4 from raid4 to raid1 is not yet supported.
  Converting the segment type for snapper_thinp/raid5 from raid5 to raid1 is not yet supported.
  Converting the segment type for snapper_thinp/raid6 from raid6 to raid1 is not yet supported.

# no -m flag
[root@host-112 ~]# for i in 1 10 4 5 6; do lvconvert --type raid10 snapper_thinp/raid$i; done
  Converting the segment type for snapper_thinp/raid1 from raid1 to raid10 is not yet supported.
  Converting the segment type for snapper_thinp/raid10 from raid10 to raid10 is not yet supported.
  Converting the segment type for snapper_thinp/raid4 from raid4 to raid10 is not yet supported.
  Converting the segment type for snapper_thinp/raid5 from raid5 to raid10 is not yet supported.
  Converting the segment type for snapper_thinp/raid6 from raid6 to raid10 is not yet supported.

# -m flag
[root@host-112 ~]# for i in 1 10 4 5 6; do lvconvert -m 1 --type raid1 snapper_thinp/raid$i; done
  snapper_thinp/raid1 already has image count of 2.
  device-mapper: reload ioctl on (253:40) failed: Invalid argument
  Failed to suspend snapper_thinp/raid10 before committing changes
  '--mirrors/-m' is not compatible with raid4
  '--mirrors/-m' is not compatible with raid5
  '--mirrors/-m' is not compatible with raid6

Nov 19 11:35:34 host-112 kernel: device-mapper: raid: Reshaping arrays not yet supported. (device count change)
Nov 19 11:35:34 host-112 kernel: device-mapper: table: 253:40: raid: Unable to assemble array: Invalid superblocks
Nov 19 11:35:34 host-112 kernel: device-mapper: ioctl: error adding target to table

# -m flag
[root@host-112 ~]# for i in 1 10 4 5 6; do lvconvert -m 1 --type raid10 snapper_thinp/raid$i; done
  snapper_thinp/raid1 already has image count of 2.
  device-mapper: reload ioctl on (253:40) failed: Invalid argument
  Failed to suspend snapper_thinp/raid10 before committing changes
  '--mirrors/-m' is not compatible with raid4
  '--mirrors/-m' is not compatible with raid5
  '--mirrors/-m' is not compatible with raid6

Nov 19 11:35:24 host-112 kernel: device-mapper: raid: Reshaping arrays not yet supported. (device count change)
Nov 19 11:35:24 host-112 kernel: device-mapper: table: 253:40: raid: Unable to assemble array: Invalid superblocks
Nov 19 11:35:24 host-112 kernel: device-mapper: ioctl: error adding target to table


Version-Release number of selected component (if applicable):
3.10.0-327.el7.x86_64
lvm2-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
lvm2-libs-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
lvm2-cluster-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-libs-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-event-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-event-libs-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-persistent-data-0.5.5-1.el7    BUILT: Thu Aug 13 09:58:10 CDT 2015
cmirror-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
sanlock-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
sanlock-lib-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
lvm2-lockd-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015

Comment 1 Heinz Mauelshagen 2016-07-06 14:33:37 UTC

Code's done and in review/integration.

Comment 3 David Teigland 2016-07-25 16:28:38 UTC

Now that we've formalized all the permitted primary lvconvert operations, and split each into a unique code path, one of the next steps is adding option validation within each of those paths.  Unless this is more than a nuisance, I'd suggest doing this after 7.3.

Comment 6 RHEL Program Management 2020-12-15 07:38:38 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

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