From owner-freebsd-questions@FreeBSD.ORG Wed Mar 30 16:05:58 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A971416A4CE for ; Wed, 30 Mar 2005 16:05:58 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 716E643D1D for ; Wed, 30 Mar 2005 16:05:58 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id ED6D853366; Wed, 30 Mar 2005 08:05:56 -0800 (PST) Date: Wed, 30 Mar 2005 08:05:56 -0800 From: Kris Kennaway To: Andrea Venturoli Message-ID: <20050330160556.GA688@xor.obsecurity.org> References: <424AACD1.3060802@netfence.it> <20050330134259.GA66640@xor.obsecurity.org> <424ACEF8.60601@netfence.it> <20050330141626.GB73682@xor.obsecurity.org> <424AE8FA.8080306@netfence.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline In-Reply-To: <424AE8FA.8080306@netfence.it> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org cc: Kris Kennaway Subject: Re: mksnap_ffs woes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2005 16:05:58 -0000 --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 30, 2005 at 06:59:22PM +0100, Andrea Venturoli wrote: > >The snapshot code was intended to support background fsck and that > >alone. It's also optionally used by the dump code, but it was not > >written as a general-purpose live filesystem snapshot service. >=20 > Ok. > I just think that this, as well as the disclaimer about it being alpha=20 > code and the access locks, should be mentioned in the Handbook. Reading= =20 > that chapter or mksnap_ffs's manual, I didn't get it and I suspect=20 > people might get the idea that it is stable code, which provides some=20 > functionality that it doesn't. The 'alpha' part is what I meant about this file being out of date. It is stable and widely used, but that doesn't mean there are not bugs. > So, if for instantaneous you mean at a specific time, I don't care at=20 > all wether the image is made an hour earlier or later. All I'd like is=20 > coherence. Isn't this usually done by dumping the database state and then backing that up, instead of trying to back up the live database? Kris --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCSs5kWry0BWjoQKURAs6bAJ9azLH9ZGyHqjK4JvKkDUVzF65JXgCeIY6u KADV5KtzuBfLPCmQk8cZea8= =L/HP -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt--