fsck hangs when a bad fid is encountered
dormando at rydia.net
Sat Sep 8 06:23:05 UTC 2007
> It appears that whenever a bad fid is encountered (ie
> no corresponding entry in the file_on table), it just
> gets stuck logging more and more SRCH and NOPA entries
> to the fsck_log.
> If we delete the bad fid from the file table, it will
> continue until it hits another bad fid.
> Is this normal? We started fsck by doing "mogadm fsck
Can you provide a subset of your fsck log? How long did you wait? How
many devices do you have? Did you see any specific errors?
I'm pretty sure it shouldn't do that :)
More information about the mogilefs