X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=L5Kn HttGCz1lNnpKwfyXdnZSCCuIl5NaI+/3lSE3U52q0w53QwlnWAAYVQGTLAKknhWG krD0kCyByhJrcfWGPavinBktl3p+yWy7RvK6vQCtkYJYFililGPaylNRv9klGJuq llWQNksSC+wz1Q7SIXYIqQ+YhF1+vZkF867+mJY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; s=default; bh=PMbGr4dTFf jEoudKxDCx85W9sDY=; b=yGk2EIab5jvgay2XzjJ85WN/8mK8008rTHX6q4IPpo VcA9jK4mjTdQ6LcF7AeAC8yRo4cVz0FfuSlf9dw8VJ8D5QNA062aa/zMqEtKcfub hWukWEwu0MtBO7OgbuIpP/2jEsGOXaILv1zv/UcA7F8Vtcm1Xo77eToEoJuhCrlj 8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=BAYES_20,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mail.spocom.com Date: Mon, 20 Apr 2015 16:38:49 -0700 From: Gary Johnson To: cygwin AT cygwin DOT com Subject: Re: tar zxvf won't work with Redhat generated compressed tar file Message-ID: <20150420233848.GB5293@phoenix> Mail-Followup-To: cygwin AT cygwin DOT com References: <969800560 DOT 20150420222609 AT yandex DOT ru> <509379965 DOT 20150420235036 AT yandex DOT ru> <55356CBB DOT 9030601 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes On 2015-04-20, Murthy Gandikota wrote: > >> Then it looks like you have a DOUBLE-compressed file. That is, someone > >> took a .tar.gz file, and ran THAT through gzip again (which seldom does > >> anything except make a LARGER file - because the first round of > >> compression removed any redundancy). Tar cannot read a > >> double-compressed stream, but breaking things into two steps lets you > >> get back to a single compressed stream, where the tar call then > >> auto-decompresses because you weren't supplying an explicit 'z' the > >> second time around. To prove it, try: > >> > >> gunzip mytar > >> tar zxvf mytar > >> > >> and if it still untars with an explicit decompression, then you have > >> proven that your original file was double-compressed. Also, if I'm > >> right about double compression, then mytar.gz would likely be slightly > >> larger than mytar (rather than the usual case of the .gz being > >> noticeably smaller). > >> > >> -- > >> Eric Blake eblake redhat com +1-919-301-3266 > >> Libvirt virtualization library http://libvirt.org > >> > > > > Yes, Sir. It did untar properly. So the problem is with the > > server compressing during the download (I get the file from a > > http server)? > > Thanks a lot for your help > It would be doubly nice if cygwin handled it ;-) It seems gunzip > had no problem recognizing the file as double compressed. > Thanks all for the help. I think you misunderstand. Gunzip decompresses once. As Eric wrote, tar recognizes compressed files and will decompress them automatically even without specifying a compression flag such as 'z'. The second decompression is done by tar, not by gunzip. Regards, Gary -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple