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:
Large file systems that have millions of files can take days for fsck.gfs2 to check. There should be some way for fsck.gfs2 to estimate the time it will take to check a given file system before committing to days of downtime.
Version-Release number of selected component (if applicable):
How reproducible:
Easily
Steps to Reproduce:
1. Fill a large device (100T+) with millions of files
2. start fsck.gfs2 on it
3. wait...
Actual results:
Expected results:
Additional info:
I'm not sure that there is any way to generate an accurate estimate. We need to be very careful here not to give the wrong impression of how long it will take, since that would be worse than not giving an estimate at all.
Closing this as a duplicate of the general fsck.gfs2 performance work, as it's essentially the same issue.
*** This bug has been marked as a duplicate of bug 1721973 ***