bz tarball recovery

John D Jones III unixgeek1972 at gmail.com
Mon Dec 14 10:02:10 MST 2009


On 12/14/2009 09:57 AM, Russel Caldwell wrote:
>> Maybe it wasn't created correctly. In other words, maybe it isn't bz.
>>
>> Are you doing tar xvfj tarball.tar.bz? Try letting tar auto-detect the
>> format by doing just tar xvf tarball.tar.bz
>>
>> You could also try using the file command to double check the file
>> format.
>>
>> When I do file myDocs.bz it returns:
>>      
> bzip2 compressed data, block size = 900k
>
> When I do file myDocs.bz it returns:
>
> bzip2 compressed data, block size = 900k
>
>
>   When I do tar xfj myDocs.bz it returns:
>
> bzip2: Data integrity error when decompressing.
>
> tar: Unexpected EOF in archive
>
> tar: Error is not recoverable: exiting now
>
>
>   When I do tar xvf myDocs.bz it returns:
>
> tar: myDocs/: Cannot read: Is a directory
>
> tar: At beginning of tape, quitting now
>
> tar: Error is not recoverable: exiting now
>
>
>   When I do bzip2 -tvv myDocs.bz to check the integrity of the file the final
> line of output says:
>
> [139: huff+mtf rt+rld]data integrity (CRC) error in data
>
>
>   I've tried to use 'bzip2recover' and as far as I can tell there seems to be
> four blocks of corrupted data.
>
> /*
> PLUG: http://plug.org, #utah on irc.freenode.net
> Unsubscribe: http://plug.org/mailman/options/plug
> Don't fear the penguin.
> */
>    
Sounds to me like an incomplete file. Perhaps the transfer was 
interrupted for the very last part of the file.

-- 
Thanks,
John D Jones III
unixgeek1972 at gmail.com
-- May the flies of a thousand camels befriend he who ruins your day.




More information about the PLUG mailing list