I’ve got an artchive with a z suffix and I can’t seem to decompress it. I know this sounds silly. Ark does not know how either. I tried the tar command with no succes (but I figured out that I could compress data to get a z suffix archive.)
Let us ignore first the suffix, what does the file command tell you
about that archive?
For example
file name_of_the_archive.z
of course using its real name.
–
PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.2 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.3 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.2 | GMA4500
Use the ‘uncompress’ command on .Z files.
Good luck.
Yes, I know that it’s an archive using UN*X compress. What I’m not sure on is how to tell CPIO or TAR to decompress it. I’d like an example of decompressing it on the command line. I tried working with one of the examples but it was no good.
On 2013-06-05 22:26, ballsystemlord wrote:
>
> Yes, I know that it’s an archive using UN*X compress. What I’m not sure
> on is how to tell CPIO or TAR to decompress it. I’d like an example of
> decompressing it on the command line. I tried working with one of the
> examples but it was no good.
As Martin said, you should verify first that it is really a “compress” file.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On Wed, 05 Jun 2013 20:26:03 +0000, ballsystemlord wrote:
> I tried working with one of the examples but it was no good.
What error message did you get when you tried?
What is the output of:
file [filename]
(Replace [filename] with the name of your file)
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Here’s all the terminal output/input
cpio -idv very_large_data_file.z
cpio: Malformed number �h��j��l
tar -tvf very_large_data_file.z
tar (child): cannot run compress: No such file or directory
tar (child): trying gzip
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
tar -xf very_large_data_file.z
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
tar -x -Z -f very_large_data_file.z
tar (child): compress: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
On 2013-06-18 17:26, ballsystemlord wrote:
>
> Here’s all the terminal output/input
Not all. Jim asked for the output of
file [filename]
and you did not.
Please use code tags for printouts and commands. Advanced forum editor,
‘#’ button. Posting in Code Tags - A Guide
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On Tue, 18 Jun 2013 15:26:01 +0000, ballsystemlord wrote:
> Here’s all the terminal output/input
It would be useful if you gave the output of the command I specified:
file very_large_data_file.z
That will tell us what the system thinks the file is. If it’s really
named “very_large_data_file.z”, it’s probably not a tar file, compressed
or not.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Sorry Jim,
I forgot to run the file program.
Here’s the output:
file very_large_data_file.z
very_large_data_file.z: compress'd data 16 bits
As suggested by ab
uncompress very_large_data_file
On 2013-07-04 00:26, syampillai wrote:
>
> As suggested by ab
>
> Code:
> --------------------
>
> uncompress very_large_data_file
>
> --------------------
file very_large_data_file.z
very_large_data_file.z
file very_large_data_file
The first line we have. Now the next two.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
The file command reports
Compressed data 16 bit
On 2013-07-12 19:16, ballsystemlord wrote:
>
> The file command reports
>
>
> Code:
> --------------------
>
> Compressed data 16 bit
>
> --------------------
At the speed you answer, and as we have to repeat our requests several
times because you do it wrong, maybe by next year we will have your
problem solved. Sigh… it is you who want help with solving your
problem, we should not be having to push you ahead!
We have the output of:
file archive.z
what we want is that you expand that file with uncompress, so that you
get “archive”:
uncompress archive.z
And when that is done, that you run
file archive
Please do it and answer NOW, today, not next month. I don’t want to
have to read again the entire thread to remember what this was about.
And please, complete answers. Post the command and result in the same
code tag block.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On 2013-07-12 19:38, Carlos E. R. wrote:
> On 2013-07-12 19:16, ballsystemlord wrote:
> Please do it and answer NOW, today, not next month. I don’t want to
> have to read again the entire thread to remember what this was about.
>
> And please, complete answers. Post the command and result in the same
> code tag block.
We want you to do this:
> cer@Telcontar:~/tmp/ballsystemlord> file initrd-cer.gz
> initrd-cer.gz: gzip compressed data, from Unix, last modified: Tue Sep 21 11:22:57 2010, max compression
> cer@Telcontar:~/tmp/ballsystemlord> gunzip initrd-cer.gz
> cer@Telcontar:~/tmp/ballsystemlord> file initrd-cer
> initrd-cer: ASCII cpio archive (SVR4 with no CRC)
> cer@Telcontar:~/tmp/ballsystemlord>
I don’t have compress installed, so I did a sample with gzip.
NOW go and do the same with your file, changing whatever needs to be
changed. Now, please.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
uncompress very_large_data_file.z
file very_large_data_file
very_large_data_file: ASCII text
It now contains 5000000 space charecters Hex value 0A
Now with gunzip
gunzip very_large_data_file.z
gzip: very_large_data_file already exists; do you wish to overwrite (y or n)?
y
file very_large_data_file
very_large_data_file: ASCII text
It now contains 5000000 space charecters Hex value 0A
Perhaps I have a bad archieve?
I’ll reget it.
On 2013-07-18 17:16, ballsystemlord wrote:
> It now contains 5000000 space charecters Hex value 0A
> Perhaps I have a bad archieve?
> I’ll reget it.
So it looks…
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Nope, I regot it and redecompressed it with the same result, Thanks though!
On 2013-07-25 23:26, ballsystemlord wrote:
>
> robin_listas;2572956 Wrote:
>> On 2013-07-18 17:16]
>> So it looks…
>>
>
>
> Nope, I regot it and redecompressed it with the same result, Thanks
> though!
Unless the decompress tool is the wrong one, which would not be
surprising, as the old unix compress is not used in Linux.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)