From owner-freebsd-stable@FreeBSD.ORG  Sat Jul 16 17:13:26 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3DB9F16A41C
	for <freebsd-stable@freebsd.org>; Sat, 16 Jul 2005 17:13:26 +0000 (GMT)
	(envelope-from mkb@mkbuelow.net)
Received: from luzifer.incubus.de (incubus.de [80.237.207.83])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BFBA343D45
	for <freebsd-stable@freebsd.org>; Sat, 16 Jul 2005 17:13:25 +0000 (GMT)
	(envelope-from mkb@mkbuelow.net)
Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de
	[84.170.134.9])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by luzifer.incubus.de (Postfix) with ESMTP id A9E4932913;
	Sat, 16 Jul 2005 19:16:17 +0200 (CEST)
Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1])
	by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id
	j6GHDduK001732; Sat, 16 Jul 2005 19:13:39 +0200 (CEST)
	(envelope-from mkb@drjekyll.mkbuelow.net)
Received: (from mkb@localhost)
	by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GHDcti001731;
	Sat, 16 Jul 2005 19:13:38 +0200 (CEST) (envelope-from mkb)
Date: Sat, 16 Jul 2005 19:13:38 +0200
From: Matthias Buelow <mkb@incubus.de>
To: Paul Mather <paul@gromit.dlib.vt.edu>
Message-ID: <20050716171338.GF752@drjekyll.mkbuelow.net>
References: <20050715224650.GA48516@outcold.yadt.co.uk>
	<200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net>
	<20050716133710.GA71580@outcold.yadt.co.uk>
	<20050716141630.GB752@drjekyll.mkbuelow.net>
	<1121530912.17757.32.camel@zappa.Chelsea-Ct.Org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1121530912.17757.32.camel@zappa.Chelsea-Ct.Org>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-stable@freebsd.org
Subject: Re: dangerous situation with shutdown process
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jul 2005 17:13:26 -0000

Paul Mather wrote:

>on reboot.  (Actually, what I find to be more inconvenient is the
>resynchronisation time needed for my geom_mirror, which takes a lot
>longer than a fsck.)  I understand that fsck delays for large file
>systems is the major impetus behind the journalling work, not as a fix
>for a perceived data consistency problem.

Well... I have lost a few (ca. 3) UFS filesystems due to power loss
or a kernel crash in the past but interestingly those were all on
SCSI (and in the pre-softupdates era, so mounted with sync metadata
updates, where this Shouldn't Happen[tm] either..) I've also seen
ext2fs (which doesn't have safeguards against fs corruption) on
Linux zapped often by power loss and haven't seen a statistically
higher number of corrupted ext2fs than ufs.  So the whole thing is
a bit hard to quantify. However, I'm all for reducing the possibility
of corruption when it could be done, programmatically.

mkb.