Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 137256 - unresolvable (cyclical) error in gfs-fsck
unresolvable (cyclical) error in gfs-fsck
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: gfs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: AJ Lewis
GFS Bugs
Depends On:
  Show dependency treegraph
Reported: 2004-10-26 18:57 EDT by Erling Nygaard
Modified: 2010-01-11 22:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-03 11:58:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
file containing a file system that has block conflicts (83.69 KB, application/octet-stream)
2004-10-28 15:18 EDT, Jonathan Earl Brassow
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:659 normal SHIPPED_LIVE Updated GFS packages 2004-12-03 00:00:00 EST

  None (edit)
Description Erling Nygaard 2004-10-26 18:57:33 EDT
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:

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 15:14:36 EDT
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 15:18:44 EDT
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 15:31:38 EDT
Fixed in 5.2.1, 6.0, and 6.1
Comment 4 Tim Powers 2004-12-03 11:58:45 EST
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.


Note You need to log in before you can comment on or make changes to this bug.