From owner-freebsd-questions@FreeBSD.ORG Wed Nov 17 05:50:49 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 05DA216A4D1 for ; Wed, 17 Nov 2004 05:50:49 +0000 (GMT) Received: from mail23.syd.optusnet.com.au (mail23.syd.optusnet.com.au [211.29.133.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5915343D31 for ; Wed, 17 Nov 2004 05:50:46 +0000 (GMT) (envelope-from syncman@optusnet.com.au) Received: from [192.168.0.7] (c211-30-137-44.belrs1.nsw.optusnet.com.au [211.30.137.44]) (authenticated bits=0)iAH5oSjo012996; Wed, 17 Nov 2004 16:50:40 +1100 Message-ID: <419B8175.6060506@optusnet.com.au> Date: Wed, 17 Nov 2004 16:51:01 +0000 From: Andrew Sinclair User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway , questions@freebsd.org References: <419A5AAB.7080409@optusnet.com.au> <20041116213536.GG17125@xor.obsecurity.org> In-Reply-To: <20041116213536.GG17125@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 5.3-RC2 tar breaks operation with "(null)" 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, 17 Nov 2004 05:50:49 -0000 Kris Kennaway wrote: >On Tue, Nov 16, 2004 at 07:53:15PM +0000, Andrew Sinclair wrote: > > >>Hi everybodi! >> >> At work I use a Windows eXPensive machine... >> I burned this tar dump onto a CD-RW... >> I'm using the new tar from 5.3-RC2 to read from the mounted CD-RW... >>It seems to have a problem with null blocks... >> >>bash-2.05b$ tar -xvf /dvdrom/20041116.tgz >>... >>x Ocean Care Day/OCD website/Website/OCD Photos/Presentation.ppt: (null) >>tar: (null) >>bash-2.05b$ >> >> I remembered that tar uses four blocks of 0x00 to indicate the end >>of an archive on a sequential device... >> >> I might be able to get around it with another tar but... >> >> > >Try an updated version of bsdtar, either by updating to 5.3-STABLE or >installing the bsdtar port. Alternatively, use gtar. > >Kris > > <>I checked the changelog for that. There is a minor change to its handling of failed writes to the archive, which is quite the opposite of what I am trying to do. My disc is unsuprisingly screwed and the drive/filesystem returns zero filled blocks where it fails to read. I managed to work around it with dd and gtar: dd if=/dvdrom/20041116.tgz of=/home/shared/mec/20041116.tgz gtar --ignore-zero --ignore-failed-read -xvf /home/shared/mec/20041116.tgz So a PPT and a PNG were garbled. No big deal. Since bsdtar is now the default Tape ARchiver, shouldn't it include the options of its predecessor? I would assert --ignore-zero on plain files and allow --ignore-failed-read at least.