From owner-freebsd-current@FreeBSD.ORG  Tue Apr 12 19:51:23 2005
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 8383B16A4CF
	for <current@FreeBSD.org>; Tue, 12 Apr 2005 19:51:23 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CCF8A43D5C
	for <current@FreeBSD.org>; Tue, 12 Apr 2005 19:51:22 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j3CJpCCY036689;
	Tue, 12 Apr 2005 12:51:18 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200504121951.j3CJpCCY036689@gw.catspoiler.org>
Date: Tue, 12 Apr 2005 12:51:12 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: scottl@samsco.org
In-Reply-To: <425BE215.4090406@samsco.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: current@FreeBSD.org
cc: kris@obsecurity.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
	<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: Tue, 12 Apr 2005 19:51:23 -0000

On 12 Apr, Scott Long wrote:
> Kris Kennaway wrote:

>> I can take a transcript of the entire fsck next time if you like :-)
>> (it ran for more than 5 hours on the 24G drive and was still going
>> after I went to bed)
>> 
>> Kris
> 
> Don might not know that your workload involves creating and deleting
> full ports/ trees repeatedly, and those trees contain hundreds of
> tousands of inodes each.

I suspected that, especially given the inode timestamps in the partial
transcript.

> If there is a reference count leak and those
> deletions aren't ever being finalized, then there would be a whole lot
> of work for fsck to do =-)  Might also explain why disks have been
> unexpectedly filling up on package machines (like mine).

Sounds likely.  When the disk starts looking unexpectedly full, can you
unmount the file system or does the attempt fail with and EBUSY error?
What happens if you fsck the file system after it has been unmounted?
Are snapshots being used?