From owner-freebsd-current@FreeBSD.ORG Sun May 16 10:40:10 2004 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 4306616A4CE; Sun, 16 May 2004 10:40:10 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB07D43D3F; Sun, 16 May 2004 10:40:09 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i4GHdsHH004331; Sun, 16 May 2004 12:39:54 -0500 (CDT) (envelope-from dan) Date: Sun, 16 May 2004 12:39:54 -0500 From: Dan Nelson To: Scott Long Message-ID: <20040516173954.GB80376@dan.emsphone.com> References: <20040515220258.H920@ganymede.hub.org> <20040515233728.Q30269@ganymede.hub.org> <20040516163039.GE29158@dan.emsphone.com> <40A79A54.3090703@freebsd.org> <20040516170441.GA80376@dan.emsphone.com> <40A7A143.7070907@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40A7A143.7070907@freebsd.org> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Michael Hamburg Subject: Re: fsck in -current 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: Sun, 16 May 2004 17:40:10 -0000 In the last episode (May 16), Scott Long said: > Dan Nelson wrote: > >In the last episode (May 16), Scott Long said: > > > >>Actually, bgfsck unconditionally inserts a delay into every 8th i/o > >>operation to try to keep from saturating the disks. Unfortunately > >>this isn't terribly sophisticated and it results in bgfsck taking > >>an eternity whether the system is idle, loaded, or reniced. > > > >See http://dan.allantgroup.com/FreeBSD/fsck_ffs.diff for a patch > >that removes the delay if it's at the minimum value, and more fairly > >calculates disk wait time. This cuts bgfsck time from ~4 hours to > >20 minutes on my 36gb /usr. > > Looks like a reasonable fix. Do you want it reviewed and committed? Sure. I don't remember why I bumped up the max wait time to 2.5 sec, though. That's probably too long. -- Dan Nelson dnelson@allantgroup.com