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 1771324

Summary: [RHEL 7.9] Update mdadm to latest upstream
Product: Red Hat Enterprise Linux 7 Reporter: XiaoNi <xni>
Component: mdadmAssignee: XiaoNi <xni>
Status: CLOSED DUPLICATE QA Contact: Storage QE <storage-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.8CC: dledford, ffan, jbrassow, lmiksik, mariusz.dabrowski, xni
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-14 02:13: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:

Comment 3 Mariusz Dabrowski 2019-11-13 08:48:06 UTC
Hello,

we would like to include those patches in RHEL 7.8 as they are the most important fixes for mdadm issues:

imsm: fix spare activation for old matrix arrays
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=05501181f18cdccdb0b3cec1d8cf59f0995504d7

mdmon: fix wrong array state when disk fails during mdmon startup
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=ae7d61e35ec2ab6361c3e509a8db00698ef3396f

Enable probe_roms to scan more than 6 roms.
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=4ec389e3f0c1233f5aa2d5b4e63d96e33d2a37f0

Regards,
Mariusz

Comment 5 XiaoNi 2019-11-15 04:20:14 UTC
Hi Mariusz

Do you think these patches must be included in rhel7.8? If so, we can file a new bug with
specific name and more description in detail. We don't get exception flag for this bug. So
the patches you mentioned in comment3 can't be included in rhel7.8 now.

Thanks
Xiao

Comment 6 Mariusz Dabrowski 2019-11-15 09:40:04 UTC
Hello Xiao,

"imsm: fix spare activation for old matrix arrays" is the most important patch and it should be included in RHEL 7.8. Without this patch, if volume was created from drives with the same size using mdadm older than 4.1 and it became degraded, user won't be able to rebuild array with identical drive because of size calculation mismatch.

Regards,
Mariusz

Comment 7 XiaoNi 2019-11-18 14:47:19 UTC
Hi Mariusz

I filed a new bug https://bugzilla.redhat.com/show_bug.cgi?id=1773607

Thanks
Xiao

Comment 9 XiaoNi 2020-05-14 02:13:49 UTC

*** This bug has been marked as a duplicate of bug 1801605 ***