Bug 137256

Summary: unresolvable (cyclical) error in gfs-fsck
Product: [Retired] Red Hat Cluster Suite Reporter: Erling Nygaard <nygaard>
Component: gfsAssignee: AJ Lewis <157070.alewis>
Status: CLOSED ERRATA QA Contact: GFS Bugs <gfs-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: jbrassow
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-03 16:58:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
file containing a file system that has block conflicts none

Description Erling Nygaard 2004-10-26 22:57:33 UTC 
Description of problem:
looping fsck giving a "unresolvable (cyclical) error"

Version-Release number of selected component (if applicable):
GFS 5.2.1 on RHEL3

How reproducible:
unknown

Steps to Reproduce:
1. mount gfs and run stuff
2. reboot storage device that contains GFS filesystem
3. run gfs_fsck
  
Actual results:
looping fsck

Expected results:
fsck fixing problems and exiting normally

Additional info:
Ask Erling for 594M logfile containing output from fsck
Comment 1 Jonathan Earl Brassow 2004-10-28 19:14:36 UTC 
The problem was that two inodes were pointing to the same data and
both inodes existed and were linked to from a directory.

One inode would get removed, but later, because it was detected in the
FTW, it would be readded.  When the fsck was restarted, it would
happen again.

Now, when I remove the inode, I destroy the meta header as well, so
that it is considered invalid during the FTW and does not get readded.
Comment 2 Jonathan Earl Brassow 2004-10-28 19:18:44 UTC 
Created attachment 105909 [details]
file containing a file system that has block conflicts

Steps to test:
1. uncompress attachment
2 [details]. run fsck on it
3. mount the file 'mount -t gfs <file> <location> -o loop
Comment 3 Jonathan Earl Brassow 2004-10-28 19:31:38 UTC 
Fixed in 5.2.1, 6.0, and 6.1
Comment 4 Tim Powers 2004-12-03 16:58:45 UTC 
An errata 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-2004-659.html