Red Hat Bugzilla – Bug 222743
gfs_grow gets the rgindex out of order
Last modified: 2010-01-11 22:32:18 EST
Description of problem:
When gfs_grow is run to extend a GFS file system, it adds entries
to the rgindex. The problem is, it writes them in reverse block order.
That has the side-effect that gfs_fsck will report the wrong percentage
complete in pass 5. For example, if you double the size of a GFS
file system, pass 5 will report 1% complete, then 2%, etc. But when it
gets to the new rgs, it will report 99%, then 98%, then 97% until it
processes them all when it returns to 50%.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a small GFS file system
2. Use gfs_grow to grow it
3. Run gfs_fsck on it
Percentage complete can run backward.
Percentage complete should be forward.
The problem is easily fixed. Back in March 2006 when I was testing
changes to gfs_fsck rg repair, I noticed this problem and created
this patch to fix it in RHEL4:
--- main.c.~1~ 2005-01-04 04:07:07.000000000 -0600
+++ main.c 2006-03-30 11:18:34.000000000 -0600
@@ -669,7 +669,7 @@ make_rgrp(uint64_t offset, uint64_t size
rgl->rg.rg_header.mh_format = GFS_FORMAT_RG;
rgl->rg.rg_free = rgl->ri.ri_data;
- osi_list_add(&rgl->list, &rglist_new);
+ osi_list_add_prev(&rgl->list, &rglist_new);
return offset + size;
The patch unfortunately never made it to RHEL5 or anywhere.
This should be fixed so customers aren't confused by it.
Created attachment 145848 [details]
RHEL5 patch to fix the problem
Unit tested on trin-10: I used "gfs2_edit -p rgindex" to print the
rg index after the mkfs and after the gfs_grow. The dump of the
rg index was bad before the fix and correct after the fix was applied
and the same commands were rerun to make and grow the file system.
Committed to CVS at HEAD and RHEL5 (not RHEL50). Changing status to
Fixing product name. Cluster Suite components were integrated into Enterprise
Linux for verion 5.0.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.