From owner-freebsd-current@FreeBSD.ORG  Tue Sep 30 14:43:28 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 6838016A4B3
	for <freebsd-current@freebsd.org>;
	Tue, 30 Sep 2003 14:43:28 -0700 (PDT)
Received: from ganymede.hub.org (u173n10.eastlink.ca [24.224.173.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2CB5043FEC
	for <freebsd-current@freebsd.org>;
	Tue, 30 Sep 2003 14:43:25 -0700 (PDT)	(envelope-from scrappy@hub.org)
Received: by ganymede.hub.org (Postfix, from userid 1000)
	id 326A934F2D; Tue, 30 Sep 2003 18:42:21 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by ganymede.hub.org (Postfix) with ESMTP id 2F35E343CE
	for <freebsd-current@freebsd.org>;
	Tue, 30 Sep 2003 18:42:21 -0300 (ADT)
Date: Tue, 30 Sep 2003 18:42:21 -0300 (ADT)
From: "Marc G. Fournier" <scrappy@hub.org>
To: freebsd-current@freebsd.org
Message-ID: <20030930183437.Y94686@ganymede.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: 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 21:43:28 -0000


Due to an electrician flipping the wrong circuit breaker this morning, I
had my servers go down hard ... they are all -STABLE, with one of the four
taking a *very* long time to fsck:

jupiter# ps aux | grep fsck
root      361 99.0  2.3 95572 95508  p0  R+    4:21PM 121:13.21 fsck -y /dev/da0s1h
jupiter# date
Tue Sep 30 18:37:02 ADT 2003
jupiter#

Now, CPU time is rising, so I figure its still working away, and fsck
shows:

jupiter# fsck -y /dev/da0s1h
** /dev/da0s1h
** Last Mounted on /vm
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts

so it isn't finding any errors ...

A friend of mine asked if we had a journalling file system, which I told
him know, as I don't believe we do ... but are/have there been any
improvements to fsck in -CURRENT to improve performance on large file
systems (this is a 6x36G RAID5 system)?  Does UFS2 address any of this?

I've actually had a 6x18gig RAID5 file system once take 11+hrs to fsck ...
and when it was completed, everything seemed fine, with no reports of any
file or directory corruption ... it obviously did a good job of checking
the file system, just hate the lengthy downtime ...