From owner-freebsd-current@FreeBSD.ORG  Tue Sep 30 15:51:18 2003
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 AA3F316A4C0
	for <freebsd-current@freebsd.org>;
	Tue, 30 Sep 2003 15:51:18 -0700 (PDT)
Received: from ganymede.hub.org (u173n10.eastlink.ca [24.224.173.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CB2384401A
	for <freebsd-current@freebsd.org>;
	Tue, 30 Sep 2003 15:50:32 -0700 (PDT)	(envelope-from scrappy@hub.org)
Received: by ganymede.hub.org (Postfix, from userid 1000)
	id 008B0344FB; Tue, 30 Sep 2003 19:49:33 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by ganymede.hub.org (Postfix) with ESMTP
	id F1B8B3427C; Tue, 30 Sep 2003 19:49:33 -0300 (ADT)
Date: Tue, 30 Sep 2003 19:49:33 -0300 (ADT)
From: "Marc G. Fournier" <scrappy@hub.org>
To: Kevin Oberman <oberman@es.net>
In-Reply-To: <20030930221148.54E7E5D07@ptavv.es.net>
Message-ID: <20030930194544.H94686@ganymede.hub.org>
References: <20030930221148.54E7E5D07@ptavv.es.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: Improvements to fsck performance 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
	<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, 30 Sep 2003 22:51:18 -0000


On Tue, 30 Sep 2003, Kevin Oberman wrote:

> Current has two major changes re speeding up fsck.
>
> The most significant is the background operation of fsck on file system
> with soft updates enabled. Because of the way softupdates works, you are
> assured of metadata consistency on reboot, so the file systems can be
> mounted and used immediately with fsck started up in the background
> about a minute after the system comes up.

Actually, I had this blow up on my -CURRENT desktop once ... didn't have a
clue on how to debug it, so I switched from fsck -p to fsck -y to prevent
it from happening again :(

Now,I don't/wouldn't have softupdates enabled on / .. does the 'background
fsck' know to not background if softupdates are not enabled?  I'm going to
switch back to -p and look a bit closer the next time it happens (if it
happens) to see if it is/was a softupdate file system that failed, now
that I have a better idea of what I'm looking for ...

> I suspect that these enhancements may both require that soft updates be
> enabled for the file systems.

are either of these enhancements back-patchable to the 4.x fsck, or do
they require some non-4.x compatible changes to work? ... I'm at 3.5hrs
and counting right now ... any speedup would be great ...