Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Feb 2009 19:03:40 -0400 (AST)
From:      "A. Wright" <andrewhw@ieee.org>
To:        dimitrovi58 <dimitrovi58@yahoo.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: dump/restore problem
Message-ID:  <alpine.BSF.2.00.0902041858100.23800@qemg.org>
In-Reply-To: <4989F838.9040605@yahoo.com>
References:  <498854F6.1389.2357B958@d.forsyth.ru.ac.za> <20090203135121.1ade28b7@gumby.homeunix.com> <4989F838.9040605@yahoo.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

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.




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0902041858100.23800>