On Fri, Feb 18, 2005 at 11:30:04AM -0500, Eric Siegerman wrote:
> On Fri, Feb 18, 2005 at 11:36:46AM +0000, Thomas Charles Robinson wrote:
> > [an excellently clear, concise, and complete [1] problem report
> > -- thank you! -- which included the following:]
> >
> > gzip: stdin: invalid compressed data--crc error
> 
> All of tar's varied complaints appear to stem from corrupt input,
> which in turn is adequately explained by this message.
> 
> Thus, either gzip or hardware looks like the culprit.  RAM is a
> good place to look, especially considering that the data being
> backed up all resides on the Amanda server; you're giving that
> box quite a workout.  The disk and its bus (SCSI, IDE, etc.) are
> possibilities too, but less likely IMO -- I'd expect the kernel
> to detect and report the I/O errors in that case.
> 
> Not to completely rule out problems with Amanda itself -- I've
> learned never to rule *anything* out where computers are
> concerned (or humans for that matter :-/) -- but it seems
> unlikely.
> 
...
> > gzip-1.3.3-9
> 
> ... is a beta.  It might be worthwhile to try the latest released
> version, 1.2.4.  From the web page, it looks as though that
> version can't handle files over 2 GB, so you'll have to split up
> any larger DLEs.  Or just disable them for the duration of the
> test -- no loss; it's not as if you have usable backups of them
> now :-( 
> 

My Solaris 9 is supplied with gzip 1.3, no extensions and dated 1999.
Never experienced any problems.

As to a 2GB limit, as gzip is being used in a pipeline I don't think
that would apply.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)