5.2-RELEASE: Possible bug in filesystem code?
Christian Laursen
xi at borderworlds.dk
Sat Jan 17 12:34:28 PST 2004
Pete Carah <pete at altadena.net> writes:
> 2. The other source of a panic is if the background fsck detects a condition
> which would cause the "preen" fsck to abort and give the "run fsck manually"
> message at bootup, it (usually?) panics the system, usually with "freeing
> freed inode". I can't think of how to handle this case any better; this
> is a "hobson's choice" condition :-(
That can only happen in two ways. Either there is a bug in softupdates which
prevents it from working correctly, or your disks are reporting data as written
when it is in fact only in the write cache.
--
Best regards
Christian Laursen
More information about the freebsd-current
mailing list