From owner-freebsd-current@FreeBSD.ORG Tue Apr 12 00:31:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB52616A4CE for ; Tue, 12 Apr 2005 00:31:17 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 354C243D3F for ; Tue, 12 Apr 2005 00:31:17 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j3C0VFBI001777; Mon, 11 Apr 2005 19:31:15 -0500 (CDT) (envelope-from dan) Date: Mon, 11 Apr 2005 19:31:15 -0500 From: Dan Nelson To: Kris Kennaway Message-ID: <20050412003114.GD284@dan.emsphone.com> References: <20050411234512.GA23344@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050411234512.GA23344@xor.obsecurity.org> X-OS: FreeBSD 5.4-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i cc: current@freebsd.org Subject: Re: Softupdates not preventing lengthy fsck X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 00:31:17 -0000 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