Date: Mon, 11 Apr 2005 19:31:15 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Kris Kennaway <kris@obsecurity.org> Cc: current@freebsd.org Subject: Re: Softupdates not preventing lengthy fsck Message-ID: <20050412003114.GD284@dan.emsphone.com> In-Reply-To: <20050411234512.GA23344@xor.obsecurity.org> References: <20050411234512.GA23344@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Apr 11), Kris Kennaway said: > I'm seeing the following problem: on 6.0 machines which have had a lot > of FS activity in the past but are currently quiet, an unclean reboot > will require an hour or more of fscking and will end up clearing > thousands of inodes: This might be expected behaviour if the previous boot tried to do a bgfsck and failed. It should set a flag forcing a full fsck on the next boot, which will clear out the half-committed inodes from the previous crash. I see it often on 5.*. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050412003114.GD284>