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.
Description of problem:
I'm trying to modify xfs/073, to make it cover V5 xfs copy test. Then I found fs corruption when xfs_copy a V5 XFS to multiple targets(xfs_copy $dev_with_v5_xfs $target1 $target2), then xfs_repair -n will find fs corruption. V4 XFS(crc=0) no this problem.
Version-Release number of selected component (if applicable):
xfsprogs-4.5.0-8.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. mkfs.xfs -m crc=1 -d name=fsfile,file=1,size=512m
2. xfs_copy fsfile target1 target2
3. xfs_repair -n target1
4. xfs_repair -n target2
Actual results:
Step#3 and/or step$4 will find corruption
Expected results:
no corruption
Additional info:
Eric has sent a patch:
"[PATCH] xfs_copy: Fix meta UUID handling on multiple copies"
to upstream to fix this problem.
Moving to 7.4, I don't see this as a blocker for rhel7.3 - xfs_copy isn't in wide use, when used, multiple targets are rare, the corruption is immediately discoverable, and it can be worked around by doing one copy at a time.
Reproduced on xfsprogs-4.5.0-9.el7_3:
=== copying scratch device to multiple targets
Creating file <FSIMAGE1>
Creating file <FSIMAGE2>
0% ... 10% ... 20% ... 30% ... 40% ... 50% ... 60% ... 70% ... 80% ... 90% ... 100%
All copies completed.
checking new image
mounting new image on loopback
comparing new image files to old
comparing new image directories to old
comparing new image geometry to old
unmounting and removing new image
checking new image
_check_xfs_filesystem: filesystem on /mnt/test/13055.image2 is inconsistent (c)
(see /root/git/xfstests-dev/results//xfs/073.full for details)
_check_xfs_filesystem: filesystem on /mnt/test/13055.image2 is inconsistent (r)
Test passed on xfsprogs-4.5.0-11.el7 with different block size:
xfs/073 16s ... 16s
Ran: xfs/073
Passed all 1 tests
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/RHBA-2017:2206