Date: Sun, 10 Nov 2002 05:05:23 -0800 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: Nick Rogness <nick@rogness.net> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Larry Sica <lomifeh@earthlink.net>, freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem corruption Message-ID: <20021110130523.GA2417@HAL9000.homeunix.com> In-Reply-To: <20021110022411.N75268-100000@skywalker.rogness.net> References: <45812.1036861207@critter.freebsd.dk> <20021110022411.N75268-100000@skywalker.rogness.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Nick Rogness <nick@rogness.net>: > I've been running dump for years on live filesystems with FreeBSD > and never had a problem. I was not aware of any snapshot feature > available for 4.X-STABLE (only 5.0)? > > umounting a live filesystem to back it up is not a solution. What > should I be using to backup a live filesystem? In 5.0-CURRENT, you can use dump on a snapshot to get a completely consistent view of the filesystem. But when you dump a filesystem as it's changing, you get an inconsistent view of its metadata, and possibly a corrupted backup. One of many solutions is to use tar. You'll get a good backup, even though it won't exactly be an atomic snapshot. (File contents might change during the operation.) See the archives for more discussions of backup programs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021110130523.GA2417>