Linux Forums - Linux Help,Advice & support community:LinuxSolved.com

Others => Miscellaneous => Topic started by: rajesh.bahl on December 19, 2007, 05:21:12 PM

Title: Uncompression Impossible:gunzip:fade.dbf.Z:Bad table(case b)
Post by: rajesh.bahl on December 19, 2007, 05:21:12 PM
Dear All,


I received one compressed file for analysis . The filename is fade.dbf.Z.

While uncompressing it on my CentOS 5 system, I receive the error:
gunzip: fade.dbf.Z: Bad table (case b)

Is there any way we can decompress this file ?


rajesh.bahl
Title: Re: Uncompression Impossible:gunzip:fade.dbf.Z:Bad table(case b)
Post by: Ricky on December 20, 2007, 01:58:52 PM
it simply means that file is corrupt, look for another copy.
Title: Re: Uncompression Impossible:gunzip:fade.dbf.Z:Bad table(case b)
Post by: rajesh.bahl on December 20, 2007, 04:12:58 PM

That is very clear from the error itself.

What I have asked for is a solution tom decompress it. The original file has been lost as the disk of the server having this file has crashed.

Also I have been told that this file was transferred from the server to a windows machine via ftp in ascii mode. I fully agree that this is a badly corrupted file but some how we have to decompress and get data out of it.


Can some one help ?




rajesh.bahl
Title: Re: Uncompression Impossible:gunzip:fade.dbf.Z:Bad table(case b)
Post by: Ricky on December 22, 2007, 05:26:51 PM
If its corrupt... I dont' think can do much !
Title: Re: Uncompression Impossible:gunzip:fade.dbf.Z:Bad table(case b)
Post by: dragoncity99 on December 27, 2007, 04:45:12 AM
Have you used uncompress command ?

--> uncompress your-file.Z

If *.Z is your extension in this case and it is using the LZ compression. If not, u can study using the file command.

# file your-file.Z

Remember, linux use extensions as an identifier for user only. In real linux, a file without a extension will still run accordingly by its application as those applications knows how to make full use of that file (be it a binary or a text file)

If the file is corrupted like Ricky mention, u can  verify by running "md5sum" on the original file and the copied file. To make sure the file did not get corrupted during transfer.
# md5sum original-file.z

# md5sum copied-file.z