From owner-freebsd-current@FreeBSD.ORG  Sat Sep  4 06:59:12 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 37EDF16A4CE
	for <freebsd-current@FreeBSD.org>;
	Sat,  4 Sep 2004 06:59:12 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E375D43D4C
	for <freebsd-current@FreeBSD.org>;
	Sat,  4 Sep 2004 06:59:11 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i846x4nM031021;
	Fri, 3 Sep 2004 23:59:08 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200409040659.i846x4nM031021@gw.catspoiler.org>
Date: Fri, 3 Sep 2004 23:59:04 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: scrappy@hub.org
In-Reply-To: <20040904003222.J812@ganymede.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
Subject: Re: what is fsck's "slowdown"?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2004 06:59:12 -0000

On  4 Sep, Marc G. Fournier wrote:
> On Fri, 3 Sep 2004, Don Lewis wrote:

>> Would the file system in question happen to be full of UNREF files that
>> fsck is deleting?
> 
> mostly 'ZERO LENGTH DIRECTORY' ...

Hmn, this may be something else then, possibly the buffer lookup in
getdatablk().  It would be very interesting to compile/link a profiled
version of fsck and see what shows up as the hot spot.  Are you using
the default value for MAXBUFSPACE (defined in fsck.h).