From owner-freebsd-fs  Mon May 14 21:17:37 2001
Delivered-To: freebsd-fs@freebsd.org
Received: from obsecurity.dyndns.org (adsl-63-207-60-32.dsl.lsan03.pacbell.net [63.207.60.32])
	by hub.freebsd.org (Postfix) with ESMTP
	id D445E37B42C; Mon, 14 May 2001 21:17:28 -0700 (PDT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id B0FCF66C8C; Mon, 14 May 2001 21:17:27 -0700 (PDT)
Date: Mon, 14 May 2001 21:17:27 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Jordan Hubbard <jkh@osd.bsdi.com>
Cc: dillon@earth.backplane.com, kris@obsecurity.org, grog@lemis.com,
	tlambert@primenet.com, mckusick@mckusick.com,
	mi@misha.privatelabs.com, cvs-committers@FreeBSD.org,
	cvs-all@FreeBSD.org, ru@FreeBSD.org, fs@FreeBSD.org
Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc]
Message-ID: <20010514211727.A94708@xor.obsecurity.org>
References: <20010515120558.M59553@wantadilla.lemis.com> <20010514202707.B93481@xor.obsecurity.org> <200105150344.f4F3iVI45699@earth.backplane.com> <20010514205836B.jkh@osd.bsdi.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010514205836B.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Mon, May 14, 2001 at 08:58:36PM -0700
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


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

On Mon, May 14, 2001 at 08:58:36PM -0700, Jordan Hubbard wrote:
> From: Matt Dillon <dillon@earth.backplane.com>
> Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc]
> Date: Mon, 14 May 2001 20:44:31 -0700 (PDT)
>=20
> >     I have to say, just IMHO, that as much as I like the concept of a
> >     background fsck, I will never ever in my life use the feature.  I'll
>=20
> Well, there are fscks and there are fscks.  It's my impression that
> *all* a background fsck on a snapshot will ever do is return free
> blocks to the freelist.  That's it.  It won't do any one of the dozens
> of other crazy things you've probably seen fsck do in cleaning up a
> badly scrogged filesystem and hence your fear, unless I'm smoking some
> unusually strong crack, is likely unwarranted.

I think thats all it does at the moment -- we started out talking
about how to make it barf acceptibly if it found something more, and
then someone raised the question of "what if we could make the
background fsck process recover from a wider class of errors" (by
improving fsck, or rerunning a foreground fsck on the ro volume, etc),
to which Terry pointed out that it's still not enough to ensure
consistency of the already running system.

Kris

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE7AK3WWry0BWjoQKURAlqpAKCqmWai6hTKO22IUwaFbLSiuvebLACgvEb+
isyAfKUn1XLLT/VQFAIK420=
=22/G
-----END PGP SIGNATURE-----

--fdj2RfSjLxBAspz7--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message