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 1463705 - RAID RESHAPE: enable on in-use LVs
Summary: RAID RESHAPE: enable on in-use LVs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Heinz Mauelshagen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1447812 1492250 1506342
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-21 14:18 UTC by Heinz Mauelshagen
Modified: 2021-09-03 12:36 UTC (History)
11 users (show)

Fixed In Version: lvm2-2.02.175-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1447812
Environment:
Last Closed: 2018-04-10 15:20:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0853 0 None None None 2018-04-10 15:21:32 UTC

Comment 3 Heinz Mauelshagen 2017-06-21 14:24:01 UTC 
We disabled reshaping of in-use RaidLVs in RHEL7.4 as of bz1447812 because of a potential data corruption on reshaping striped RAIDs.

This bz tracks enabling it again once the deadlock fix is in.
Comment 4 Jonathan Earl Brassow 2017-06-21 16:33:23 UTC 
... but the increased functionality is scheduled for 7.5 and is not a testblocker.
Comment 7 Marian Csontos 2017-10-10 12:31:35 UTC 
Heinz, is the deadlock fix mentioned in Comment 3 in? Should this be reenabled and tested?
Comment 8 Heinz Mauelshagen 2017-10-11 13:12:52 UTC 
(In reply to Marian Csontos from comment #7)
> Heinz, is the deadlock fix mentioned in Comment 3 in? Should this be
> reenabled and tested?

Yes.

LVM2 enabled reshaping of in-use LV again with
commit 6685460f5a918393edcde50d11f5cefb3a259df8.
Comment 12 Corey Marthaler 2017-11-27 20:48:56 UTC 
Verified that online in-use reshape/takeover is again enabled in the latest lvm rpms. 

3.10.0-799.el7.x86_64
lvm2-2.02.176-4.el7    BUILT: Wed Nov 15 04:21:19 CST 2017


That said the following 7.4 issues are again back as 7.5 regressions.

bug 1514539 kernel Deadlock in reshape on single core machine
bug 1514500 kernel RAID TAKEOVER: "divide error" panic during raid0_meta -> raid10 attempt
bug 1514215 lvm2   RAID RESHAPE: potential for data corruption when adding striped raid images to offline volumes
Comment 15 errata-xmlrpc 2018-04-10 15:20:44 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/RHEA-2018:0853
Note You need to log in before you can comment on or make changes to this bug.