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:
xfs_repair progress reporting is broken.
Version-Release number of selected component (if applicable):
xfsprogs-5.0.0-10.el8.x86_64
How reproducible: Always
Steps to Reproduce:
Run xfs_repair on a large filesystem using `xfs_repair -o ag_stride=4 -t 1`
or use the (unmerged) xfstest from https://lore.kernel.org/linux-xfs/20200817075313.1484879-1-ddouwsma@redhat.com/
Actual results:
# xfs_repair -o ag_stride=4 -t 1
Phase 1 - find and verify superblock...
- reporting progress in intervals of 1 second
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- 11:14:16: scanning filesystem freespace - 4 of 4 allocation groups done
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- 11:14:16: scanning agi unlinked lists - 4 of 4 allocation groups done
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
...
Expected results:
# xfs_repair -o ag_stride=4 -t 1
Phase 1 - find and verify superblock...
- reporting progress in intervals of 1 second
Phase 2 - using internal log
- zero log...
- 12:05:06: scanning filesystem freespace - 0 of 0 allocation groups done
- 12:05:07: scanning filesystem freespace - 0 of 0 allocation groups done
- scan filesystem freespace and inode maps...
- 12:05:08: scanning filesystem freespace - 0 of 4 allocation groups done
- 12:05:08: scanning filesystem freespace - 4 of 4 allocation groups done
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- 12:05:08: scanning agi unlinked lists - 4 of 4 allocation groups done
- process known inodes and perform inode discovery...
- agno = 0
- 12:05:09: process known inodes and inode discovery - 320 of 46208 inodes done
- 12:05:09: Phase 3: elapsed time 1 second - processed 19200 inodes per minute
- 12:05:09: Phase 3: 0% done - estimated remaining time 2 minutes, 23 seconds
- 12:05:10: process known inodes and inode discovery - 320 of 46208 inodes done
- 12:05:10: Phase 3: elapsed time 2 seconds - processed 9600 inodes per minute
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 (xfsprogs bug fix and enhancement update), 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-2023:7113