From owner-freebsd-stable@FreeBSD.ORG Wed Mar 25 16:11:39 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1B871065672; Wed, 25 Mar 2009 16:11:39 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 61DC48FC21; Wed, 25 Mar 2009 16:11:39 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:d93e:519d:eeb6:9049] (unknown [IPv6:2001:7b8:3a7:0:d93e:519d:eeb6:9049]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 73F155C43; Wed, 25 Mar 2009 17:11:38 +0100 (CET) Message-ID: <49CA57BB.2070409@andric.com> Date: Wed, 25 Mar 2009 17:11:39 +0100 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b4pre) Gecko/20090324 Shredder/3.0b3pre MIME-Version: 1.0 To: "Mikhail T." References: <49C83673.3000604@aldan.algebra.com> <200903241537.36515.doconnor@gsoft.com.au> <49C87E0D.5090501@aldan.algebra.com> In-Reply-To: <49C87E0D.5090501@aldan.algebra.com> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, fs@freebsd.org Subject: Re: dump | restore fails: unknown tape header type 1853384566 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Mar 2009 16:11:40 -0000 On 2009-03-24 07:30, Mikhail T. wrote: > dump a0f - /old | restore -rf - > [...] > DUMP: 17.25% done, finished in 3:27 at Tue Mar 24 05:42:00 2009 > DUMP: 20.36% done, finished in 3:09 at Tue Mar 24 05:28:13 2009 > DUMP: 23.83% done, finished in 2:50 at Tue Mar 24 05:14:32 2009 > unknown tape header type -621260722 > abort? [yn] > > Looks like a junk value somewhere... Unitialized variable or some such. Hmm, I can't reproduce this at all; I use dump and restore quite regularly in this way, and I have never encountered this issue (except for the occasional 'expected file NNN, got file MMM', which is usually harmless). Maybe the dump output gets corrupted in some way? (E.g. faulty RAM, or disk?) If you are dumping a live filesystem, could it possibly help to add the -L option?