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.
+++ This bug was initially created as a clone of Bug #1186515 +++
Description of problem:
After running d_io on a cluster and running fsck.gfs2 on the file system I found that fsck.gfs2 often produces an error message like this:
Error: inode 99591 (0x18507) has invalid allocation goal block 204891 (0x3205b). Should be 99591 (0x18507)
On further inspection, block 204891 is actually a directory leaf block of inode 99591.
[root@host-051 tmp]# gfs2_edit -p 204891 /dev/STSRHTS16693/STSRHTS166930
Block #204891 (0x3205b) of 1308672 (0x13f800) (directory leaf)
Leaf:
mh_magic 0x01161970(hex)
mh_type 6 0x6
mh_format 600 0x258
lf_depth 5 0x5
lf_entries 14 0xe
lf_dirent_format 1200 0x4b0
lf_next 0 0x0
lf_inode 99591 0x18507
lf_dist 1 0x1
lf_nsec 668537594 0x27d912fa
lf_sec 1422389987 0x54c7f2e3
This probably doesn't need to be fixed
Version-Release number of selected component (if applicable):
gfs2-utils-3.1.7-6.el7.x86_64
How reproducible:
Easily
Steps to Reproduce:
1. run d_io -S QUICK on a GFS2 file system
2. fsck.gfs2
Actual results:
Expected results:
Additional info:
--- Additional comment from Abhijith Das on 2015-01-28 11:41:38 EST ---
fsck.gfs2 doesn't traverse the metadata tree for dirs in pass1 to be able to get at the last allocated block for it and attempts to set it to the inode block itself when it finds the i_goal value to be outside of the current rgrp. This is not desirable and fsck.gfs2 should probably leave directories alone.
Nate also reported that gfs2_convert isn't making an attempt to fix goal values either and results in zeros being set instead. The fix for that needs to be rolled in along with this bug's patch.
--- Additional comment from Abhijith Das on 2015-02-09 21:41:30 EST ---
This is an easy fix where fsck.gfs2 doesn't attempt to fix non-zero goal values for directories.
--- Additional comment from Abhijith Das on 2015-02-09 21:51:59 EST ---
This version deems an existing goal block as valid if it exists in any rgrp in the fs. It does this by checking the inode's goal block against all the rgrps in the fs. While the code tries to avoid checking all the rgrps as much as possible, if it does end up doing this often, then this becomes a very expensive operation.
The patch does the following:
1. If the computed goal_blk for a given inode is equal to the dinode's block, then we haven't really computed much and this is a worst-case correct value for the goal.
2. If we don't have a better computed goal (i.e 1. is true), we check if the existing goal block is valid using check_valid_block()
3. check_valid_block() tries to avoid running through all the rgrps by checking the following things first:
a) If the block is out of bounds of the filesystem, it's invalid.
b) If the block belongs to the same rgrp as that of the dinode, it is valid.
c) Warn the user that further investigation might take time and get her consent before finally resorting to check all the rgrps for this block.
d) If the block is found, we assume it is valid... invalid otherwise.
--- Additional comment from Abhijith Das on 2015-02-11 10:49:31 EST ---
This is a slight improvement over the first patch where check_i_goal assumes a block that falls within the fs bounds is valid for a directory's allocation goal block and skips such directories.
I'm hitting this while running the bz855381 regression test. This is the error to look for during the fsck tags.
[nate0] [fsck] Initializing fsck
[nate0] [fsck] Validating Resource Group index.
[nate0] [fsck] Level 1 rgrp check: Checking if all rgrp and rindex values are good.
[nate0] [fsck] (level 1 passed)
[nate0] [fsck] Starting pass1
[nate0] [fsck] ^M19 percent complete.^MError: inode 55120219 (0x349115b) has invalid allocation goal block 6979644 (0x6a803c). Should be
55120219 (0x349115b)
[nate0] [fsck] Invalid goal block not fixed.
[nate0] [fsck] Error: inode 55120219 (0x349115b) has invalid allocation goal block 6979644 (0x6a803c). Should be 55120219 (0x349115b)
[nate0] [fsck] Invalid goal block not fixed.
[nate0] [fsck] pass1 completed in 0.820s
Version-Release number of selected component (if applicable):
gfs2-utils-3.0.12.1-73.el6.x86_64
We're out of time to fix this bug for 6.7. We're still evaluating the proper fix for this issue in upstream, after which it'll get backported to rhel7 and rhel6. This is not a critical bug, so we can push it out to 6.8 and do a z-stream later as needed.