From owner-freebsd-stable Tue Mar 23 9:38:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B1CDA14CCD for ; Tue, 23 Mar 1999 09:38:26 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id SAA76302; Tue, 23 Mar 1999 18:38:04 +0100 (CET) (envelope-from des) To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Build of 3.1-STABLE failing? References: From: Dag-Erling Smorgrav Date: 23 Mar 1999 18:38:03 +0100 In-Reply-To: Mike Meyer's message of "Mon, 22 Mar 1999 11:42:52 -0800 (PST)" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer writes: > If you read the handbook on backups, you'll note that the recommended > backup tool is dump - because it's the only thing that does the job > right. Wrong. Dump relies on a number of assumptions which are only correct for quiescent (i.e. unmounted) file systems. If you want to use dump reliably, mirror your file system across two disks. Unmount one of them before dumping. Sync it up with the live one once the dump is complete, and remount. This procedure guarantees that the file system is in a stable, consistent state throughout the dump. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message