Date: Sun, 10 Nov 2002 19:33:11 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Nick Rogness <nick@rogness.net> Cc: Larry Sica <lomifeh@earthlink.net>, freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem corruption Message-ID: <24699.1036953191@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 10 Nov 2002 02:33:55 MST." <20021110022411.N75268-100000@skywalker.rogness.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20021110022411.N75268-100000@skywalker.rogness.net>, Nick Rogness w rites: >> The fix is to not run dump(8) on a live filesystem. You should >> either use a snapshot or umount the device. > > 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)? It works most of the time, but not always. There is no way for dump(8) to realize what has changed under its feet and therefore it sometimes ends up with a bunch of negative blocknumbers. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?24699.1036953191>