From owner-freebsd-fs@FreeBSD.ORG  Sun Sep  9 20:09:35 2007
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3EE0716A419;
	Sun,  9 Sep 2007 20:09:35 +0000 (UTC)
	(envelope-from scode@hyperion.scode.org)
Received: from hyperion.scode.org (cl-1361.ams-04.nl.sixxs.net
	[IPv6:2001:960:2:550::2])
	by mx1.freebsd.org (Postfix) with ESMTP id E23EC13C481;
	Sun,  9 Sep 2007 20:09:34 +0000 (UTC)
	(envelope-from scode@hyperion.scode.org)
Received: by hyperion.scode.org (Postfix, from userid 1001)
	id 254BF23C4AB; Sun,  9 Sep 2007 22:09:34 +0200 (CEST)
Date: Sun, 9 Sep 2007 22:09:34 +0200
From: Peter Schuller <peter.schuller@infidyne.com>
To: Kris Kennaway <kris@FreeBSD.org>
Message-ID: <20070909200933.GA98161@hyperion.scode.org>
References: <46E4225F.1020806@gmx.net> <46E42D14.5060605@FreeBSD.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk"
Content-Disposition: inline
In-Reply-To: <46E42D14.5060605@FreeBSD.org>
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: freebsd-fs@freebsd.org, Johannes Totz <jo_t@gmx.net>
Subject: Re: UFS not handling errors correctly
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Sep 2007 20:09:35 -0000


--UugvWAfsgieZRqgk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> bg fsck cannot fix arbitrary filesystem corruption.  Nor is it intended t=
o.

But is not the proposed problem that UFS caused the corruption to
begin with?

Given that updates are already done in such a way as to cause
predictable inconsistency in the event of a crash, should not
appropriate course of action in a case such as this be to panic,
unmount the fs, rollback and error out, or otherwise abort the
operation in a way the filesystem can be fsck:ed and re-mounted
(assuming the device is alive), rather than cause corruption?

--=20
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@infidyne.com>'
Key retrieval: Send an E-Mail to getpgpkey@scode.org
E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org


--UugvWAfsgieZRqgk
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFG5FL9DNor2+l1i30RAj49AJ0beAgk+Vua8EHZvXM2OIFu3tOkcACfW+4i
VBTspk6BIGd6DU6Jt9xeohs=
=DZqC
-----END PGP SIGNATURE-----

--UugvWAfsgieZRqgk--