On Tue, Apr 26, 2005 at 08:32:59AM -0500, Bryan K. Walton wrote: > 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? >
I would. Not necessarily the gzip/gunzip commands, but the packing/unpacking process. By that I mean, it could be media errors, memory errors, ... that are affecting, or have affected, the compression process. Maybe google for those error messages. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
