Bug 169047 - "Found unused inode marked in-use" while running gfs_fsck
Summary: "Found unused inode marked in-use" while running gfs_fsck
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: gfs
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Abhijith Das
QA Contact: GFS Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-22 15:07 UTC by Corey Marthaler
Modified: 2010-01-12 03:07 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-01-04 17:59:02 UTC
Embargoed:

Attachments (Terms of Use)

Description Corey Marthaler 2005-09-22 15:07:16 UTC 
Description of problem:
Nate and I have been seeing this warnings while running gfs_fsck regression
tests. Possibly related to bz 150207 however we don't see the thousands of
messages spitting out anymore. Can these messages be expected in recovery cases
or is this a true bug?


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

How reproducible:
quite often while running REG tests

Steps to reproduce:
1. create a gfs and populate with I/O
2. during I/O kill the cluster
3. bring the cluster back up but before mounting run gfs_fsck
Comment 1 Abhijith Das 2006-01-04 17:59:02 UTC 
These messages are expected behavior and this is not a true bug. When the
cluster is killed during IO, metadata is not consistent. This is fixed either by
mounting GFS (thereby replaying journals to restore consistency) or by running
gfs_fsck to fix these issues. gfs_fsck is simply reporting the inconsistencies
that it finds with the above messages.
Note You need to log in before you can comment on or make changes to this bug.