I've had the same message from tar on what were apparently erroneous backups. I believe the `obsolescent base-64 header' message is what you get whenever tar's input is corrupted, which seems to be c
Author: Toralf Lund <toralf AT procaptura DOT com>
Date: Wed, 13 Oct 2004 15:43:15 +0200
tar: Skipping to next header tar: Archive contains obsolescent base-64 headers 37800+0 records in 37800+0 records out gzip: stdin: invalid compressed data--crc error tar: Child returned status 1 tar
Author: Jean-Francois Malouin <Jean-Francois.Malouin AT bic.mni.mcgill DOT ca>
Date: Wed, 13 Oct 2004 09:54:36 -0400
* Toralf Lund <toralf AT procaptura DOT com> [20041013 09:43]: Honestly, I missed the earlier post in this thread... Which version of tar are you using? I've used the SGI provided gzip for a long tim
Author: Toralf Lund <toralf AT procaptura DOT com>
Date: Wed, 13 Oct 2004 17:07:09 +0200
[ snip ] Actually, I'm starting to suspect that gzip itself is causing the problem. Any known issues, there? The client in question does have a fairly old version, 1.2.4, I think (that's the latest
Author: Gene Heskett <gene.heskett AT verizon DOT net>
Date: Wed, 13 Oct 2004 12:32:47 -0400
You can tell amanda in the ./configuration options given, where the correct tar actually lives and it will be hardcoded into it. And to get the version from the other tar, "/usr/bin/tar --version" sh
Author: Toralf Lund <toralf AT procaptura DOT com>
Date: Thu, 14 Oct 2004 10:24:42 +0200
[ snip ] Actually, I'm starting to suspect that gzip itself is causing the problem. Any known issues, there? The client in question does have a fairly old version, 1.2.4, I think (that's the latest
Author: Toralf Lund <toralf AT procaptura DOT com>
Date: Thu, 14 Oct 2004 10:32:34 +0200
The fun part here is that I have two different tars and two different gzips - the ones supplied with the OS and "SGI freeware" variants installed on /usr/freeware (dowloaded from http://freeware.sgi.
Author: Geert Uytterhoeven <geert AT linux-m68k DOT org>
Date: Thu, 14 Oct 2004 10:33:54 +0200 (MEST)
If gzip has problems in the > 2 GiB file size areas, usually it's related to displaying statistics (try `gzip -l' on a large compressed file). I never heard of problems with the actual compression, w
Author: Toralf Lund <toralf AT procaptura DOT com>
Date: Thu, 14 Oct 2004 15:40:50 +0200
[...] I get the same kind of problem with harddisk dumps as well as tapes, and as it now turns out, also for holding disk files. And the disks and tape drive involved aren't even on the same chain. A
Author: Toralf Lund <toralf AT procaptura DOT com>
Date: Fri, 15 Oct 2004 09:55:48 +0200
[...] I get the same kind of problem with harddisk dumps as well as tapes, and as it now turns out, also for holding disk files. And the disks and tape drive involved aren't even on the same chain. A