From owner-freebsd-stable Wed Dec 29 12:31:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id DB8DE156C4 for ; Wed, 29 Dec 1999 12:31:17 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id VAA12607 for freebsd-stable@freebsd.org; Wed, 29 Dec 1999 21:31:13 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id VAA36791 for freebsd-stable@freebsd.org; Wed, 29 Dec 1999 21:11:11 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Dump problem (soft updates?) Date: 29 Dec 1999 21:11:10 +0100 Message-ID: <84dpsu$13te$1@bigeye.rhein-neckar.de> References: <199912291222.EAA22783@netcom.com> <199912291323.FAA06712@cwsys.cwsent.com> To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group wrote: > The other possibility is that the filesystem was actively being written to > while the dump was taken (very bad idea). Supposedly dump handles this quite well. I haven't stress-tested this yet, but I keep my machines in multiuser mode when running dump. No problems encountered so far. > "e**(i*pi)+1=0" ;-) -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message