From owner-freebsd-fs@FreeBSD.ORG Wed Mar 25 18:13:39 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FDDD1065673 for ; Wed, 25 Mar 2009 18:13:39 +0000 (UTC) (envelope-from hywel@hmallett.co.uk) Received: from lisbon.directrouter.com (lisbon.directrouter.com [72.249.30.130]) by mx1.freebsd.org (Postfix) with ESMTP id 4EB868FC1D for ; Wed, 25 Mar 2009 18:13:39 +0000 (UTC) (envelope-from hywel@hmallett.co.uk) Received: from localhost ([127.0.0.1]) by lisbon.directrouter.com with esmtpa (Exim 4.69) (envelope-from ) id 1LmWkp-0008He-7n for freebsd-fs@freebsd.org; Wed, 25 Mar 2009 12:19:03 -0500 Received: from 82.111.203.2 ([82.111.203.2]) by www.hmallett.co.uk (Horde MIME library) with HTTP; Wed, 25 Mar 2009 17:19:03 +0000 Message-ID: <20090325171903.x4eqs9ceo8w00c04@www.hmallett.co.uk> Date: Wed, 25 Mar 2009 17:19:03 +0000 From: Hywel Mallett To: freebsd-fs@freebsd.org References: <49C83673.3000604@aldan.algebra.com> <200903241537.36515.doconnor@gsoft.com.au> <49C87E0D.5090501@aldan.algebra.com> <49CA57BB.2070409@andric.com> In-Reply-To: <49CA57BB.2070409@andric.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.6) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - lisbon.directrouter.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - hmallett.co.uk X-Source: X-Source-Args: X-Source-Dir: 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: Wed, 25 Mar 2009 18:13:40 -0000 Quoting Dimitry Andric : > 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. Looking at the restore code (tape.c, in findinode), restore is =20 expecting a header type in the range 1-6, so the header type =20 -621260722 is way out. Assuming that findinode is being passed the =20 correct variable, it would indicate that dump is writing the header =20 (or at least the header type incorrectly). I can't work out where this =20 header is getting written though. It looks like plenty of data gets =20 written into a header (such as inode, magic number, checksum). I =20 wonder if one of these values is overflowing and overwriting the =20 header type? > > 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? It might be worth fscking the original volume (though I suspect the OP =20 has done this already), and also passing the -D option to restore, as =20 restore will then try and continue, rather than abort on getting the =20 invalid header type. Fixing the root cause would be better, but that =20 might be a workaround for now.