Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Mar 2009 17:35:25 -0500
From:      Scott Lambert <lambert@lambertfam.org>
To:        freebsd-stable@freebsd.org
Subject:   Re: dump | restore fails: unknown tape header type 1853384566
Message-ID:  <20090325223525.GM80292@sysmon.tcworks.net>
In-Reply-To: <49C99204.2050601@aldan.algebra.com>
References:  <49C83673.3000604@aldan.algebra.com> <49C98202.9040403@modulus.org> <49C98680.7020301@aldan.algebra.com> <200903251232.11418.doconnor@gsoft.com.au> <49C99204.2050601@aldan.algebra.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 24, 2009 at 10:08:04PM -0400, Mikhail T. wrote:
> That said, I point out, that for me, dump is not failing (although it 
> did hang this morning). It is the restore, which fails to read dump's 
> output:
> 
>    unknown tape header type 213474529
>    abort? [yn] n
>    resync restore, skipped 502 blocks
>    expected next file 54, got 0
>    unknown tape header type -954356454
>    abort? [yn] n
>    resync restore, skipped 29 blocks
>    expected next file 54, got 0
>    unknown tape header type -1754938223
>    abort? [yn] n
>    resync restore, skipped 482 blocks
>    expected next file 54, got 0
>    unknown tape header type -915868704
>    abort? [yn] n
>    resync restore, skipped 29 blocks
>    expected next file 54, got 0
>    unknown tape header type 1790084751
>    abort? [yn] n
>    resync restore, skipped 482 blocks
>    expected next file 54, got 0
>    unknown tape header type 903667267
>    abort? [yn] n
>    ...

If you happen to have a different version of FreeBSD on another box of
boxes, older or newer, you might try a test restore of your problem dump
file on those boxes.

If you can make a dump file which shows this bug on being fed to
restore, which doesn't have sensitive information in it, I would be
happy to download it and see if I can reproduce the problem on a few
boxes with different versions of FreeBSD here.  I had some restore
issues in May of 2008 which got resolved because I could create a dump
file which would fail to restore on a developer's system.  But that was
a different issue than you are seeing.

-- 
Scott Lambert                    KC5MLE                       Unix SysAdmin
lambert@lambertfam.org




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090325223525.GM80292>