Jon,
        I'm afraid I was a little hasty with my emails.  Last night, I started
gunzip the file and then went home for the evening.  A few hours later,
I ssh'd into my backup server and, upon seeing that the gunzip process had
finished, I issued the file cmd on the unzipped file, which correctly told
me that the file was gnu tar file.  Then, as I mentioned in my email last
night, I got the error messages when tried to extract with tar.
        HOWEVER, upon returning to the office this morning to my open shell
window (where I started the gunzip before leaving the office last night),
I saw errors:

amanda:/u10# gunzip < sharedata > sharedata.unzipped
gunzip: stdin: invalid compressed data--crc error
gunzip: stdin: invalid compressed data--length error

I apologize.  I wrongly assumed that because the gunzip process had
finished last night and that the file cmd saw the output as a gnu tar
file, that all was well.  So, should I assume that gzip/gunzip is the
problem here?

Thanks!
Bryan Walton
 

On Tue, Apr 26, 2005 at 01:38:43AM -0400, Jon LaBadie wrote:
> On Mon, Apr 25, 2005 at 07:38:34PM -0500, Bryan K. Walton wrote:
> > Hi Jon,
> >     Thanks for the email.  I tried what you said, please read
> > below:
> > 
> 
> I was afraid it would not work.
> 
> This will not be comforting, but you are not alone.
> 
> I googled for the "obsolescent base-64 header" message and found
> hundreds (thousands?) of hits.  May have been some earlier, but
> at least as early as 2001.  Most were mailing list help requests.
> I followed several, none to successful conclusion.
> 
> Some said it was a defect in gzip/gunzip or the builtin compressor.
> Some said it was data corruption as the data were archived.
> Some said it was the lack of using the "j" option.
> Some said it was a version thing, try a different one.
> And Jorg Shilling said try to unpack it with his 'star' program.