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:
> 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.