Bug 169687 - gfs_fsck: ondisk and fsck bitmaps differ at block XXXXX: never fixed
gfs_fsck: ondisk and fsck bitmaps differ at block XXXXX: never fixed
Status: CLOSED CURRENTRELEASE
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: gfs (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Feist
GFS Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-10-01 00:51 EDT by Axel Thimm
Modified: 2010-01-11 22:07 EST (History)
0 users

See Also:
Fixed In Version: 6.1.2-0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-11-07 12:07:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Axel Thimm 2005-10-01 00:51:12 EDT
Description of problem:
Running gfs_fsck finds some differening bitmaps and gfs_fsck offers to fix them.
Even though answering yes to this offer a subsequent gfs_fsck run show the same
errors.

Version-Release number of selected component (if applicable):
GFS-6.1.0-0

How reproducible:
Always

Steps to Reproduce:
1.Manage to get differing bitmaps
2.Run gfs_fsck and answer y to all questions or run gfs_fsck -y
3.Do 2. again
  
Actual results:
The bitmaps still differ

Expected results:
The second run should be clean, or the errors maekred as non-recoverable.

Additional info:
I won't be able to do much further testing, as we are about to wipe the
filesystem and recreate it.

The gfs filesystem is not mounted by any cluster member during gfs_fsck.
Comment 1 Chris Feist 2005-11-07 12:07:52 EST
I am unable to replicate and believe this bug has been fixed in the latest GFS
release (GFS-6.1.2-0.i386)
Comment 2 Axel Thimm 2005-11-08 05:12:53 EST
I haven't since encountered it again, but OTOH I haven't managed to corrupt the
filesystem again. If I see it again, I'll reopen.

Is there any other information I should gather in this case?

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