Description of problem: The problem described in bug #436383 (RHEL4) and bug #434962 (RHEL5) introduces corruption into a gfs file system. Today's gfs_fsck is unable to repair that damage, and I think it needs to. Version-Release number of selected component (if applicable): RHEL4 How reproducible: Easily (now that I know the trick). Steps to Reproduce: 1. Follow the steps listed in bug #436383 to corrupt a file system 2. Run gfs_fsck on the corrupt file system Actual results: gfs_fsck's resource group analysis says "(passed)" and no corruption is detected. [root@exxon-01 /home/bob]# gfs_fsck /dev/exxon_vg/exxon_lv Initializing fsck Can't seek to last block in file system: 4309132281 Unable to determine the boundaries of the file system. Expected results: gfs_fsck should detect and repair the damage gracefully. Additional info: I've got a prototype patch that does this. The RHEL4 version is attached to bug #436383. It still needs some testing.
Requesting flags for inclusion into 4.8.
Still time to get this into cluster 4.7 so devel acking and switching the flag.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
I tested this on the exxon-0{2,3} cluster and pushed the patch to git at the RHEL4 branch for inclusion into 4.7. Changing status to modified.
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. http://rhn.redhat.com/errata/RHBA-2008-0804.html