PLEX86  x86- Virtual Machine (VM) Program
 Plex86  |  CVS  |  Mailing List  |  Download  |  Linux  |  Newsgroups

rescue damaged tar file 7295


Your Ad Here

Your Ad Here

rescue damaged tar file 7296
I have two copies of the archive, on two machines. (Both slackware linux 10.2.) It exhibits the same behavior and...

Michael Powe

I think you can forget about it. Modern compressors operate by specifying a position and length of previous data to copy as new data, using a window of from 4k to 64k or more into the old data (measured from the point of expansion). Once the data is fouled that reference is gone, and there is no way to recover.

The same applies to LZW compression, although the mechanism is different. There there is a remote chance that the compressor has detected a poor compression ratio and decided to reinitialize its tables, in which case some recovery would be possible. However that mechanism hasn't been used seriously for 20 years or so, due to patent problems.

That is one advantage of the zip format, i.e. each individual compressed file stands alone, so an error will only lose one file. With the tar format all files are basically concatenated into one, and the result may then be compressed.

To avoid this sort of foul up in the future, you would be well advised to insist on ECC memory in all your systems.

-- "If you want to post a followup via groups.google.com, don't use the broken "Reply" link at the bottom of the article. Click on "show options" at the top of the article, then click on the "Reply" at the bottom of the article headers." - Keith Thompson



Your Ad Here

List | Previous | Next

rescue damaged tar file 7296

Linux groups from Newsgroups

The #1 Usenet Provider on the Internet

rescue damaged tar file