[Linux-cluster] Found unlinked inode

David Teigland teigland at redhat.com
Wed Sep 26 13:41:27 UTC 2007

On Wed, Sep 26, 2007 at 10:33:41AM +0200, Borgstr?m Jonas wrote:
> Hi again,
> After stress testing a gfs filesystem for 24 hours fsck.gfs complains
> about "Found unlinked inode".  This scared me so I reran the test again
> but got the same result. 
> My test consists of two nodes running bonnie++, postgresql and pgbench
> against a single file system. Every five minutes one of the nodes is
> shot.
> The weird part is that on both occasions the thing fsck.gfs complained
> about was an "unlinked inode" corresponding to a postgresql pid file.
> This is a file created (and deleted) every time postgresql is failed
> over to another node. It is also the last file on the filesystem being
> deleted when postgresql was shutdown before the filesystem was umounted
> and fsck.gfs was run.
> Can anybody explain why this pid file triggered this fsck error twice
> and not any of the thousands of files created and deleted by bonnie++?
> Does this mean the filesystem is corrupt, or is this an expected
> behavior for files deleted directly before a filesystem is umounted?

I don't think fsck recovers the journal, and journal recovery would most
likely fix this up.  Do you see this if you do a mount/unmount before
running fsck?


More information about the Linux-cluster mailing list