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.
xfs_check is currently broken for multi-inode-record situations (e.g., 64k block sizes on supported arches). To reproduce, format a large block size fs and run check:
# mkfs.xfs -f -b size=64k <dev>
# xfs_db -c check <dev>
bad magic number 0 for inode 1152
bad magic number 0 for inode 1153
bad magic number 0 for inode 1154
bad magic number 0 for inode 1155
bad magic number 0 for inode 1156
bad magic number 0 for inode 1157
bad magic number 0 for inode 1158
bad magic number 0 for inode 1159
bad magic number 0 for inode 1160
bad magic number 0 for inode 1161
...
This occurs due to some broken logic in upstream xfsprogs commit bb2f98b7 ("xfs_db: make check work for sparse inodes"). Since this patch adds support for sparse inodes and sparse inodes are not yet supported in rhel, the best course of action is probably to revert/drop the patch from xfsprogs in rhel 7.3.
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://rhn.redhat.com/errata/RHBA-2016-2431.html
xfs_check is currently broken for multi-inode-record situations (e.g., 64k block sizes on supported arches). To reproduce, format a large block size fs and run check: # mkfs.xfs -f -b size=64k <dev> # xfs_db -c check <dev> bad magic number 0 for inode 1152 bad magic number 0 for inode 1153 bad magic number 0 for inode 1154 bad magic number 0 for inode 1155 bad magic number 0 for inode 1156 bad magic number 0 for inode 1157 bad magic number 0 for inode 1158 bad magic number 0 for inode 1159 bad magic number 0 for inode 1160 bad magic number 0 for inode 1161 ... This occurs due to some broken logic in upstream xfsprogs commit bb2f98b7 ("xfs_db: make check work for sparse inodes"). Since this patch adds support for sparse inodes and sparse inodes are not yet supported in rhel, the best course of action is probably to revert/drop the patch from xfsprogs in rhel 7.3.