From owner-freebsd-current@FreeBSD.ORG Wed Oct 24 22:16:56 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30FDA16A418; Wed, 24 Oct 2007 22:16:56 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (unknown [IPv6:2001:41c8:1:548a::2]) by mx1.freebsd.org (Postfix) with ESMTP id C4A9313C4C6; Wed, 24 Oct 2007 22:16:55 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.draftnet (unknown [IPv6:2a01:348:10f:1::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id E04D830180; Wed, 24 Oct 2007 23:16:52 +0100 (BST) Message-ID: <471FC451.6090200@cran.org.uk> Date: Wed, 24 Oct 2007 23:16:49 +0100 From: Bruce Cran User-Agent: Thunderbird 2.0.0.6 (X11/20070809) MIME-Version: 1.0 To: Tim Kientzle References: <471CF3F3.6070803@cran.org.uk> <8cb6106e0710222017p133ddccyc973c6ebcd23e270@mail.gmail.com> <471DCED7.2020500@freebsd.org> In-Reply-To: <471DCED7.2020500@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: josh.carroll@gmail.com, current@freebsd.org Subject: Re: bsdtar can't handle files >8GB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2007 22:16:56 -0000 Tim Kientzle wrote: > Josh Carroll wrote: >>> tar: Unrecognized archive format: Inappropriate file type or format >>> tar: Error exit delayed from previous errors. >> >> Confirmed in RELENG_7 as well. Interestingly enough, if the file >> inside the tarball is nothing but zeros (dd if=/dev/zero ...), I don't >> get this error. However, it doesn't work either. The resulting file >> is 0 bytes, rather than 10 GB of \0. > > Try the attached patch, which I think fixes this > problem. Thanks, the patch fixes the problem on RELENG_7 on my computer. -- Bruce