Update question
I received several answers from people suggesting the tar-archive was ftp-ed
in ascii mode instead of in binary mode. This however was not the case.
As indicated by several people the simplest thing would be to recreate the
archive again on the sending node, check the cheksum there, ftp the file,
check the checksum again on the receiving site and untar again.
This however is quite a job for the mentioned archive, cause it's quite a
job to recreate the archive because it consists of a large number of files
of which some are removed already from the system where the archive was
created.
So I'm basically looking for a way to extract the corrupted archive without
recreating and re-sending the archive ..
***********************************
Original question
> Admins,
>
> When trying to unpack a tar-archive from disk (approx 740 Megs) which was
> ftp-ed from another machine to one of our 4.0-D alpha 2100 we received the
> following error message :
>
> tar: Ready for volume 2
> tar: Type "go" when ready to proceed (or "q" to abort): go
> tar: [offset 704m+30k+779]: Continuing
> tar: DECEDI_000807133323_archive : This doesn't look like a tar archive
> tar: DECEDI_000807133323_archive : Skipping to next file...
> tar: Memory allocation failed for extended data while reading : Not enough
> space
>
> There isn't a second volume so the archive looks corrupted. Are there any
> ways to recover the file, or are there any other tricks (beyond recreating
> the archive on the sending machine and unpacking it again) to extract the
> archive. Any help is appreciated.
>
> Regards,
> Gert-Jan Hilbrands
> KPN DC
>
Received on Thu Sep 21 2000 - 14:35:02 NZST