I'm trying to uncompress a file using

gunzip GCF_000746645.1_ASM74664v1_genomic.fna.gz

... but I get the following error:

gzip: GCF_000746645.1_ASM74664v1_genomic.fna.gz is set-group-ID on execution - ignored

I've learned that "set-group-ID on execution" refers to something related to permissions on the server, but I'm not entirely sure how so and what I should do.

I am using zcat to output the contents of a rather large .gz compressed text file. I am piping the output to grep and searching for a specific string. Below is the command I am running. dylan@xaelah:/media/dylan/ExtHD$ zcat wpaPasswords2.gz | grep baconisdelicious The command runs for a while and then exits with the following error. gzip: wpaPasswords2.gz: unexpected end of file I have also tried piping the output to the tail command, which with default options it completes with output, but not with the last 10 lines of the compressed files, it outputs 10 lines but not the last 10 lines. If I pipe the output to 'tail -n 1' such as: dylan@xaelah:/media/dylan/ExtHD$ zcat wpaPasswords2.gz | tail -n 1 I get the same error message of gzip: wpaPasswords2.gz: unexpected end of file While the command runs I watch the output of htop and the bottle neck is I/O, the computer is not running out of ram so I am unclear of how exactly to determine what the cause of this issue is. I have checked the logs and have not found anything of value. The reason I am trying to do all of this is because I am going to combine several very large .gz files while sorting them and removing duplicates however I want to make sure my process will work before running my scripts over gigs and gigs of data. Any advice would be appreciated, thanks!

I have an Operating system image of size 2.5G. I have a device with a limited size. Thus I was looking for the best possible solution for providing the compression. Below are the commands and results of their compression: 1.tar with gzip: tar c Os.img | gzip --best > Os.tar.gz This command returned an image of 1.3G. 2.Xz only: xz -z -v -k Os.img This command returned an image of 1021M. 3.Xz with -9: xz -z -v -9 -k Os.img This command returned an image of 950M. 4.tar with Xz and -9: tar cv Os.img | xz -9 -k > Os.tar.xz This command returned an image of 950M. 5.tar with Xz -9 and -e: xz -z -v -9 -k -e Os.img This command returned an image of 949M. 6.lrzip: lrzip -z -v Os.img This command returned an image of 729M. Is there any other possible best solution or command line tool ( preferable ) for the compression?

root@server # tar fcz bkup.tar.gz /home/foo/ tar: Removing leading `/' from member names How can I solve this problem and keep the / on file names ?

I would like to use GNU Parallel to process a huge .gz or .bz2 file. I know I can do: bzcat huge.bz2 | parallel --pipe ... But it would be nice if there was a way similar to --pipe-part that can read multiple parts of the file in parallel. One option is to decompress the file: bzcat huge.bz2 > huge parallel --pipe-part -a huge ... but huge.bz2 is huge, and I would much prefer decompressing it multiple times than storing it uncompressed.

I used gzip to compress an image which is quite huge still. dd if=/dev/sda2 bs=1M | gzip -c -9 > sda2.dd.img.gz then I changed the partitioning of the Drive because I wanted to install Linux. And when trying to decompress and write it to the former (smaller) partition gunzip sda2.dd.img.gz >/dev/sda2 (using > instead of dd, as described here, its content is first written to another file (instead of directly to the partition as I expected). The Problem: the Partition where the zipped file is on is to. small. I could use a external media but that will take more time. But would prefer to write the decompressed data to the partition directly. So I decided to get more info about zipping itself first. but it left me even more confused (see my first response here) Can anyone give any hint, please ? thanks in advance,

I tarred one file with:

tar cf My-tarball.tar path/to/file.txt

Then compressed it:

gzip My-tarball.tar

But when i decompress it and extract it

gunzip My-tarball.tar.gz
tar -xf My-tarball.tar

the file is in a bad format, on Vim it shows a lot of:

^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^

and so on... I'm really worried if a I lost my file T-T, i have no backup, stupid from my part What am i missing? What can i do? **P.S.:** all of the process was run on a NTFS disk mounted with lowntfs-3g if it helps Thanks in advance

I was attempting to untar a .tar.gz file, but came across this error: gzip: stdin: unexpected end of file tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now The tar.gz file includes a .tar file, which when untarred results in: tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now I tried both –ignore-zeros and –ignore-failed-read, although they both didn't work. Is there any way I could extract this file even if it is corrupted? The file type in question: .tar.gz: Gzip Compressed Data, from a UNIX system.

I recently realized that the RPM packages shifted from gzip-compression to xz-compression a few years ago. I need to check is the compression type of an RPM package that I have. I also need to check what compression type is considered by my system when it is trying to unpack an RPM file.

More and more tar archives use the xz format based on LZMA2 for compression instead of the traditional bzip2(bz2) compression. In fact *kernel.org* made a late "*Good-bye bzip2*" announcement, 27th Dec. 2013 , indicating kernel sources would from this point on be released in both tar.gz and tar.xz format - and on the main page of the website what's directly offered is in tar.xz. Are there any specific reasons explaining why this is happening and what is the relevance of gzip in this context?

I needed to compress/archive a folder, so I ran the following command:

gzip -v --rsyncable --fast -r myFolder/ -c > myFolderArchive.gz

...foolishly thinking this was going to do just what I thought it would: an archive of myFolderArchive and its files recursively. It even had a nice output:

./myFolder/file1 ... 80%
./myFolder/file2 ... 20%
...

Opening the archive later however, I only see a single file in it. A quick search led me to understand my mistake: GZip (or I guess, myself) has taken every file, compressed it, and concatenated them one by one into a single file, essentially. Losing all file/directory structure. In the meantime, I've rm -r'd the original folder. All I have now is myFolderArchive.gz. Would anyone see a way to take that archive, and potentially reconstruct the original set of files, from the myFolderArchive.gz file's content, now that it's all mixed into a single GZipped file? I do still have access to the original disk (for a limited time) and could potentially attempt to recover at least the original directory structure (filesystem is ext4). Technically, the content/data itself is in myFolderArchive.gz, it would "just" need to be sliced right...

I have multiple tar.gz archives, the size of each archive is approximately 40 GB: v1.0-trainval01_blobs.tgz v1.0-trainval01_blobs.tgz ... v1.0-trainval10_blobs.tgz I can unpack each archive and get the following directory structure: v1.0-trainval01_blobs samples sweeps v1.0-trainval02_blobs samples sweeps ... v1.0-trainval10_blobs samples sweeps This unpacking will consume many hours, even days. But this is not enough! Next I have to merge samples and sweeps folders: v1.0-trainval_all_blobs samples sweeps And this is time-consuming operation again... Do I can unpack contents of all tar.gz in v1.0-trainval_all_blobs via the single command?

I'm trying to identify parts of a MySQL DB that take most space in GZipped dumps that I need to frequently save and restore so that I can archive some tables partially. I have a suspicion that different tables are compressed better or worse depending on their content so their uncompressed size is not very relevant here. Is there any way I can map CREATE TABLE or INSERT statements in the DB dump to the file positions in the .sql.gz file? Something like gunzip where {0} is the current position of the db.sql.gz file that gunzip is reading from