From owner-freebsd-questions Mon Mar 12 17:53:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.nbrewer.com (sparge.nbrewer.com [208.42.68.70]) by hub.freebsd.org (Postfix) with ESMTP id C067A37B736 for ; Mon, 12 Mar 2001 17:53:33 -0800 (PST) (envelope-from chris@nbrewer.com) Received: by mail.nbrewer.com (Postfix, from userid 1001) id 653EE383071; Mon, 12 Mar 2001 19:53:32 -0600 (CST) Date: Mon, 12 Mar 2001 19:53:32 -0600 From: Christopher Farley To: Dan Nelson Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 2GB limit on gzip? Message-ID: <20010312195330.A82645@northernbrewer.com> Mail-Followup-To: Christopher Farley , Dan Nelson , freebsd-questions@FreeBSD.ORG References: <20010312165812.A82168@northernbrewer.com> <20010312173441.A25752@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010312173441.A25752@dan.emsphone.com>; from dnelson@emsphone.com on Mon, Mar 12, 2001 at 05:34:41PM -0600 Organization: Northern Brewer, St. Paul, MN Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson (dnelson@emsphone.com) wrote: > If you really mean you're getting "invalid compressed data--length > mismatch", you can safely ignore it. It's been fixed in the latest > gzip source, I believe. I've been gzipping files over 4gb for quite a > while on my 4.2 boxes with no problems. What I actually mean is gunzip: stdin: invalid compressed data--format violated Decompression ceases at this point. I get a similar failure with bunzip2: bunzip2: Data integrity error when decompressing. Input file = fs-dump.gz2, output file = fs-dump -- Christopher Farley www.northernbrewer.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message