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:
xfs/032 fails on ppc64/ppc64le host with xfsprogs-4.5.0-2.el7, "xfs_db -c check" after test reports bad magic number and other errors like below:

...
bad magic number 0 for inode 3147775
root inode 1792 is not a directory
block 0/7 type unknown not expected
...
allocated inode 1792 has 0 link count

A simpler reproducer would be:
# on ppc64 or ppc64le host
mkfs -t xfs -s size=32768 -b size=65536 -d size=1g -f /dev/sda5
xfs_db -c check /dev/sda5

Both v4 and v5 xfs could reproduce.

xfsprogs-3.2.2-2.el7 works fine, xfs_db check reports no error.

Version-Release number of selected component (if applicable):
xfsprogs-4.5.0-2.el6.ppc64
kernel-3.10.0-439.el7

How reproducible:
100%

Steps to Reproduce:
1. see description
2.
3.

Actual results:
xfs_db -c check reports errors

Expected results:
no error

Additional info:
Upstream kernel and xfsprogs have the same issue. I first noticed this with xfsprogs-4.5.0-rc1. And I've reported this (along with other issues) to xfs list, but no response.

http://oss.sgi.com/archives/xfs/2016-03/msg00063.html

Now a bug is needed to track the failure for RHEL7.

Created attachment 1169051 [details]
xfs-032.full

This is probably a dup of bug #1346927

Thanks for the report, we'll revert the problematic patch.

Can you see if this bug persists with xfsprogs-4.5.0-4.el7 or later?  Hopefully it is just a dup of #1346927

Thanks,
-Eric

Confirmed xfsprogs-4.5.0-5.el7 passed xfs/032, looks like it's indeed a dup of bug 1346927. I'm closing it as so. Thanks Eric!

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