From owner-freebsd-fs@FreeBSD.ORG Thu Mar 26 17:01:10 2009 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A3A8106566C; Thu, 26 Mar 2009 17:01:10 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id 4530D8FC15; Thu, 26 Mar 2009 17:01:09 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 26 Mar 2009 17:01:07 +0000 (GMT) Date: Thu, 26 Mar 2009 17:01:06 +0000 From: David Malone To: "Mikhail T." Message-ID: <20090326170106.GA28100@walton.maths.tcd.ie> References: <49C83673.3000604@aldan.algebra.com> <200903241537.36515.doconnor@gsoft.com.au> <49C87E0D.5090501@aldan.algebra.com> <49C92060.4060303@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49C92060.4060303@aldan.algebra.com> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: Danny Braniss , freebsd-stable@freebsd.org, fs@freebsd.org Subject: Re: dump | restore fails: unknown tape header type 1853384566 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Mar 2009 17:01:10 -0000 On Tue, Mar 24, 2009 at 02:03:12PM -0400, Mikhail T. wrote: > Same problem: > > restore -rf ibmo.0.2009-03-24.dump > load: 0.55 cmd: restore 11303 [nbufkv] 3.53u 3.91s 4% 27980k > unknown tape header type 213474529 > abort? [yn] > > Please, advise. Thanks! Yours, Hi Mikhail, If you actually need to get a dump back that restore can't read, you can try the "-D" option that I added a few years ago. Dump and restore expect things to be in a block format, but if (say) dump outputs a few bytes into the stream due to a bug, then the entire end of the dump can become unreadable. The -D option to restore tells it to try hard to get back in sync again. I'd guess you've tripped over either a bug in dump or restore. If you can file a PR, particularly with access to a sample dump, then I can have a look and see if I can figure out what's going on. Daid.