From owner-freebsd-questions@FreeBSD.ORG Wed Feb 25 09:24:14 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD8E116A4CE for ; Wed, 25 Feb 2004 09:24:14 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DAEE43D1F for ; Wed, 25 Feb 2004 09:24:14 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i1PHODwu077657; Wed, 25 Feb 2004 11:24:13 -0600 (CST) (envelope-from dan) Date: Wed, 25 Feb 2004 11:24:13 -0600 From: Dan Nelson To: Mike Schroll Message-ID: <20040225172413.GA44342@dan.emsphone.com> References: <403CB39B.5000606@mail.rit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <403CB39B.5000606@mail.rit.edu> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: gzip GB file limit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2004 17:24:14 -0000 In the last episode (Feb 25), Mike Schroll said: > I recently backed up my data before blowing away a partition with > tar -cvf - /docs |gzip -> /docs.tgz > -- it went through fine, no errors. > > I've now discovered that the gzip which ships with FreeBSD 5.x base, > 1.2.4 has a 2GB or 4GB file size limit on the file it creates... > the file created by that command was 4.9GB, > now when I extract it I get > gzip: docs.tgz: invalid compressed data--format violated It must have gotten corrupted somewhere else. gzip has been largefile-safe for years. The header will has a 32-bit rollover problem with the filesize (i.e. gzip -l won't show the right size), but you should be able to gzip and gunzip files over 4gb with no other problems. -- Dan Nelson dnelson@allantgroup.com