From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 08:42:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0690816A4CE for ; Tue, 20 Jul 2004 08:42:37 +0000 (GMT) Received: from mail009.syd.optusnet.com.au (mail009.syd.optusnet.com.au [211.29.132.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4F3243D48 for ; Tue, 20 Jul 2004 08:42:35 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i6K8gPm16862; Tue, 20 Jul 2004 18:42:25 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i6K8AqVd006286; Tue, 20 Jul 2004 18:10:52 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i6K8AqX1006285; Tue, 20 Jul 2004 18:10:52 +1000 (EST) (envelope-from pjeremy) Date: Tue, 20 Jul 2004 18:10:51 +1000 From: Peter Jeremy To: Tim Kientzle Message-ID: <20040720081051.GB3001@cirb503493.alcatel.com.au> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <40FC9FC2.8050400@kientzle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FC9FC2.8050400@kientzle.com> User-Agent: Mutt/1.4.2i cc: Andrey Chernov cc: current@freebsd.org Subject: Re: NEW TAR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 20 Jul 2004 08:42:37 -0000 On Mon, 2004-Jul-19 21:29:54 -0700, Tim Kientzle wrote: >I have some ideas about sparse file handling, >but they're not gtar-compatible. (The gtar >approach has a number of drawbacks. The primary >one being that on many systems it requires reading >the entire file twice, once to find holes and again >to actually archive the file. Actually, it's not possible to accurately determine the holes in a file by reading it - you can't differentiate between a hole and a allocated block of zeroes. What you need is a (new) syscall that invokes a new VOP_... and returns a bitmap of allocated blocks. This would be non-trival unfortunately. -- Peter Jeremy