From owner-freebsd-questions@FreeBSD.ORG Wed Feb 4 23:02:39 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85E06106566C for ; Wed, 4 Feb 2009 23:02:39 +0000 (UTC) (envelope-from andrewhw@ieee.org) Received: from mailserv.mta.ca (mailserv.mta.ca [138.73.1.1]) by mx1.freebsd.org (Postfix) with ESMTP id 505498FC21 for ; Wed, 4 Feb 2009 23:02:39 +0000 (UTC) (envelope-from andrewhw@ieee.org) Received: from [138.73.29.51] (helo=qemg.org) by mailserv.mta.ca with esmtp (Exim 4.61) (envelope-from ) id 1LUqlR-0000IG-2z; Wed, 04 Feb 2009 19:02:37 -0400 Date: Wed, 4 Feb 2009 19:03:40 -0400 (AST) From: "A. Wright" Sender: andrew@qemg.org To: dimitrovi58 In-Reply-To: <4989F838.9040605@yahoo.com> Message-ID: References: <498854F6.1389.2357B958@d.forsyth.ru.ac.za> <20090203135121.1ade28b7@gumby.homeunix.com> <4989F838.9040605@yahoo.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: dump/restore problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2009 23:02:39 -0000 Ivan; > when I started a migration to new HDD, according few how-tos, I got the > following warning: > > # dump -0Lauf - /dev/ad0s1f | restore -rf - When debugging dump/restore problems, it is always best to dump to a file, and then restore from the file -- this allows you to see which of dump and restore is printing which message. I would guess that the "Header with wrong dumpdate" is this issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/118087 More surprising is: > warning: ./.snap: File exists > *expected next file 141455, got 146* > DUMP: 2.86% done, finished in 3:35 at Thu Feb 5 01:44:32 2009 What exactly is your .snap entry? Is it actually a directory, or do you have a file called .snap that is getting in the way? The "expected next file" message indicates inode numbers out of sequence, which I would guess also come from restore -- if the warning about .snap comes from dump, then I would encourage you to make sure that dump cleanly creates its archive (to a file) before spelunking in the restore error messages. If you are short of space and are using several partitions on your new drive, just format the largest and place the output files there while you experiement. Andrew.