Michael Schaller wrote:
I found out that this was a problem of my tar.
I backed up with GNUTAR and "compress server fast".
AMRESTORE restored the file but TAR (on the server!) gave some horrible
messages like yours.
I transferred the file to the original machine ("client") and all worked
fine.
I guess this is a problem of different tar versions ...
That's strange and freightening! Tar is supposed to be a portable
format! Especially gnutar -- there are indeed differences with normal
OS-supplied tar formats, but only to overcome limits in filesize, path
name length etc.; but the same version of gnutar on different
architectures should be able to read each others files.
I'm not 100% sure what happens if you compile tar on an architecture
without largefile support on and try to restore a file exceeding such
a limit.
Are you sure you used the correct version of tar. I've called mine
"gtar" to avoid confusion with the OS-supplied tar (actually, amanda
even uses "amgtar", which is a link to the correct version, or a
wrapper that does some pre/post processing if needed on e.g. database
DLE's).
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
