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.

Essentially the identical bug reported to Debian in spring 2017 affects RHEL6.9, with ext4.  We suffered ext4 filesystem corruption when doing the same steps as in the referenced Debian bug.  Please backport the fix.

Acked. The patch looks simple enough and harmless even for ZStream:

https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=8ab072507706fb826eee05eb369429ad0a7a406a

> Acked. The patch looks simple enough and harmless even for ZStream:
> https://sourceware.org/git/?p=lvm2.git [...]

Coincidentally, sourceware.org itself was the machine hit by this bug.

Marcel, could we get this on ACL, please? It must have been missed as it was in MODIFIED since long time ago.

FYI, it is included in 6.9.z, so it would be a regression to exclude this patch.

The 6.10 package is the same as the 6.9.z, except the version/release.

As the lvm2 component is not on ACL, there is no need to release the fix in rhel-6.10 because the lvm2 package will be taken from the rhel-6.9.z branch during rhel-6.10 compose.

However if the lvm2 appears on ACL till the rhel-6.10 GA date, the fix for this bug needs to be released in rhel-6.10 as well to avoid regressions.

My proposal here will be to keep this bug open until the rhel-6.10 GA date and then close it as CURRENT_RELEASE. This should be done automatically as part of the rhel-6.10 cleanup after the GA.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days