Sponsored Content
Full Discussion: Validate compressed files
Top Forums Shell Programming and Scripting Validate compressed files Post 303042269 by Master_Mind on Friday 20th of December 2019 03:03:59 AM
Old 12-20-2019
Thanks Neo, But its not working

Code:
gzip -t file.zip

gzip: file.zip: not in gzip format

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

import compressed files using pipe

I am trying to import compressed files using a pipe on a server, IBM AIX UNIX 3.4, with very little disk space The command is: nohup cat xaa xab xac xad xae xaf xag | uncompress - > imp_pip & Then the imp_pip file is used in the import statement, files=imp_pip Does this statement... (0 Replies)
Discussion started by: pengwyn
0 Replies

2. UNIX for Dummies Questions & Answers

delete compressed files from year 2005

I'm trying to delete files that were created/modified in the year 2005 that we compressed and have the .Z extension on them. I tried using the awk utility but the syntax is incorrect. I don't know how to use a wildcard to capture all the compressed files. Here's the code I used ( ls -lR |... (5 Replies)
Discussion started by: igidttam
5 Replies

3. UNIX for Dummies Questions & Answers

diff on compressed files with tar.gz ext

how can I find out what is the difference between two tar.gz files without uncompressing them. thank you. (7 Replies)
Discussion started by: rakeshou
7 Replies

4. UNIX for Dummies Questions & Answers

multi part compressed files

Hi there, not sure if I am in the right place but here is my question. I have a file that is over 100mb and my host does not allow FTP of files above 100mb so I thought I would use a compression utility to compress it into smaller parts say 10mb each, upload them and then re-assemble them on... (7 Replies)
Discussion started by: gffb
7 Replies

5. UNIX for Dummies Questions & Answers

To view compressed files

Hello All I compressed a file hello by using compress command compress hello ( enter ) i got the file as hello.z 1. My question is how can i see the file hello.z 2. How can i uncompress it back to change it to filename hello thanks (4 Replies)
Discussion started by: supercops
4 Replies

6. UNIX for Dummies Questions & Answers

Count number of compressed files in a tar.gz archive

Hi Folks, I have a tar.gz compressed file with me, and I want to know the number of files in the archive without uncompressing it. Please let me know how I can achieve it. Regards RK Veluvali (5 Replies)
Discussion started by: vrk1219
5 Replies

7. UNIX for Dummies Questions & Answers

How to distribute compressed files as text?

Hello everybody, I've seen some text documents where they publish blocks of text and tell you to save it as "file.tgz" for example, and when you decompress the file, it actually works. How is that done? is there a program? Because i tried cat and doesn't work, tried less, more, hexedit and... (2 Replies)
Discussion started by: semash!
2 Replies

8. UNIX for Dummies Questions & Answers

Extracting data from many compressed files

I have a large number (50,000) of pretty large compressed files and I need only certain lines of data from them (each relevant line contains a certain key word). Each file contains 300 such lines. The individual file names are indexed by file number (file_name.1, file_name.2, ... ,... (1 Reply)
Discussion started by: Boltzmann
1 Replies

9. UNIX for Dummies Questions & Answers

Reading compressed files during a grep search

All, The bottom line is that im reading a file, storing it as variables, recursively grep searching it, and then piping it to allow word counts as well. I am unsure on how to open any .zip .tar and .gzip, search for keywords and return results. Any help would be much appreciated! Thanks (6 Replies)
Discussion started by: ryan.lee
6 Replies

10. Shell Programming and Scripting

Search compressed files with awk and get FILENAME

I have many compressed files I want to search using awk and want to print some file contents along with the filename it came from on each output record (I simplified awk command). Here are the results with the files uncompressed: awk '{print FILENAME, $0}' test*.txt test1.txt from test1... (3 Replies)
Discussion started by: mjf
3 Replies
expand_dump(8)						      System Manager's Manual						    expand_dump(8)

NAME
expand_dump - Produces a non-compressed kernel crash dump file SYNOPSIS
/usr/sbin/expand_dump input-file output-file DESCRIPTION
By default, kernel crash dump files (vmzcore.#) are compressed during the crash dump. Compressed core files can be examined by the latest versions of debugging tools that have been recompiled to support compressed crash dump files. However, not all debugging tools may be upgraded on a given system, or you may want to examine a crash dump from a remote system using an older version of a tool. The expand_dump utility produces a file that can be read by tools that have not been upgraded to support compressed crash dump files. This non-compressed version can also be read by any upgraded tool. This utility can only be used with compressed crash dump files, and does not support any other form of compressed file. You cannot use other decompression tools such as compress, gzip, or zip on a compressed crash dump file. Note that the non-compressed file will require significantly more disk storage space as it is possible to achieve compression ratios of up to 60:1. Check the available disk space before running expand_dump and estimate the size of the non-compressed file as follows: Run tests by halting your system and forcing a crash as described in the Kernel Debugging manual. Use an upgraded debugger to determine the value of the variable dumpsize. Multiply this vale by the 8Kb page size to approximate the required disk space of the non-compressed crash-dump. Run expand_dump and pipe the output file to /dev/null, noting the size of the file that is printed when expand_dump completes its task. RETURN VALUES
Successful completion of the decompression. The user did not supply the correct number of command line arguments. The input file could not be read. The input file is not a compressed dump, or is corrupted. The output file could not be created or opened for writing and truncated. There was some problem writing to the output file (probably a full disk). The input file is not formated consistantly. It is probably corrupted. The input file could not be correctly decompressed. It is probably corrupted. EXAMPLES
expand_dump vmzcore.4 vmcore.4 SEE ALSO
Commands: dbx(1), kdbx(8), ladebug(1), savecore(8) Kernel Debugging System Administration expand_dump(8)
All times are GMT -4. The time now is 02:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy