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.
When using ext4 as the backing device for a loopback xfs filesystem, it gets corrupted during an xfstests run.
A short reproducer is to configure the test device as xfs, and make the scratch device a 10G loopback filesystem, hosted on ext4. Then run ./check 167 168
This is due the discards issued by mkfs.xfs during the test, which punches holes in the ext4 file, and ends up corrupting it. It's fixed upstream by:
commit 5f95d21fb6f2aaa52830e5b7fb405f6c71d3ab85
Author: Lukas Czerner <lczerner>
Date: Mon Mar 19 23:03:19 2012 -0400
ext4: rewrite punch hole to use ext4_ext_remove_space()
When using ext4 as the backing device for a loopback xfs filesystem, it gets corrupted during an xfstests run. A short reproducer is to configure the test device as xfs, and make the scratch device a 10G loopback filesystem, hosted on ext4. Then run ./check 167 168 This is due the discards issued by mkfs.xfs during the test, which punches holes in the ext4 file, and ends up corrupting it. It's fixed upstream by: commit 5f95d21fb6f2aaa52830e5b7fb405f6c71d3ab85 Author: Lukas Czerner <lczerner> Date: Mon Mar 19 23:03:19 2012 -0400 ext4: rewrite punch hole to use ext4_ext_remove_space()