From owner-freebsd-hackers Tue May 5 01:04:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18179 for freebsd-hackers-outgoing; Tue, 5 May 1998 01:04:28 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18157 for ; Tue, 5 May 1998 01:04:16 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id JAA18220; Tue, 5 May 1998 09:04:01 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <354EC800.8FC1F9C8@tdx.co.uk> Date: Tue, 05 May 1998 09:04:16 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Tom CC: Benjamin Greenwald , freebsd-hackers@FreeBSD.ORG Subject: Re: dump/restore broken? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > Perhaps, but dump/restore is broken for large filesystems. Perhaps one > of the dump/restore advocates should fix it before a new user is swayed by > the rhetoric into using dump/restore, only to watch restore core dump on > large dumps. Just how large a file system does this need testing on? - I run it on 2 x 9Gig UFS systems and one 12Gig UFS filesystem - and it's not failed yet (Typically the file systems are at around 70% capacity when running dump). If dump/restore really is broken - I'd kinda like to know now, although the results of our last disaster recovery test (i.e. take a blank machine and 2 tapes) were successful... The only time I've seen problems with dump/restore was with a dodgy SCSI bus, in which case the dump would work fine - but the restore would either claim the tape was "not a dump tape", or it would core dump/panic at varying parts into the restore... Fixing the termination on the bus fixed this though - and it has been thoroughly tested... Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message