Date: 17 Jan 2004 21:34:23 +0100 From: Christian Laursen <xi@borderworlds.dk> To: freebsd-current@freebsd.org Subject: Re: 5.2-RELEASE: Possible bug in filesystem code? Message-ID: <86oet2z54g.fsf@borg.borderworlds.dk> In-Reply-To: <20040117142950.GA28573@users.altadena.net> References: <20040117142950.GA28573@users.altadena.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Pete Carah <pete@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86oet2z54g.fsf>