Re: Problems with amrestore and sparse files

Kevin Dalley wrote:

I used amrestore to recover a file and received error message which
look like this:

Extracting from file /backup/20050125170301/condor._.5
tar: ./var/cache/apt/pkgcache.bin: invalid sparse archive member
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
tar: ./var/cache/apt-proxy/.apt-proxy/backends/debian/packages.db: invalid 
sparse archive member
tar: Skipping to next header

I'm using GNU tar 1.14.


Yes, gnutar 1.14 has this known bug when encountering a
sparse file in the archive during recovery.

The archive itself however is fine. You can restore the files
using gnutar 1.13.25 or 1.15.1.



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