Dege, Robert C. wrote:

Backup using Compression Fast with GNUTAR
=========================================
*) Amrecover restoring data from an image in the holding disk -
successful
*) Amrecover restoring data from an image written to an AIT-2 tape -
fails

Backup using no Compression with GNUTAR
=======================================
*) Amrecover restoring data from an image in the holding disk -
successful
*) Amrecover restoring data from an image written to an AIT-2 tape -

successful


I would do one more test: create 1 very big file, 1 Gbyte or more,
with garbage, calculate md5sum; and repeat the 4 steps above, each
time checking the md5sum of the restored file.

The reason I suggest this is that single-bit errors (because
bad RAM, or an overheated processor or alpha particles, or the
warranty on the chicken you sacrified has passed...) have immediate
effect on gzip, but go unnoticed many times in other situations.

It sure takes time to test this, but it helps ruling out hardware
problems, with very similar symptoms.


--
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          *
***********************************************************************