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 [email protected] _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
