From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 11:09:35 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 0341B16A4CE for ; Fri, 23 Jul 2004 11:09:35 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D718043D60 for ; Fri, 23 Jul 2004 11:09:33 +0000 (GMT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.11/8.12.11) with ESMTP id i6NB9VTM041973; Fri, 23 Jul 2004 15:09:31 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.11/8.12.11/Submit) id i6NB9VSc041972; Fri, 23 Jul 2004 15:09:31 +0400 (MSD) (envelope-from ache) Date: Fri, 23 Jul 2004 15:09:31 +0400 From: Andrey Chernov To: Ian FREISLICH Message-ID: <20040723110931.GB41806@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Ian FREISLICH , Garrett Wollman , current@FreeBSD.ORG, Daniel Lang References: <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.26.0.10; VDF 6.26.0.40 (host: pobrecita.freebsd.ru) cc: current@FreeBSD.ORG cc: Daniel Lang cc: Garrett Wollman 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: Fri, 23 Jul 2004 11:09:35 -0000 On Thu, Jul 22, 2004 at 02:37:00PM +0200, Ian FREISLICH wrote: > Garrett Wollman wrote: > > < said: > > > > > I do not see, why it is important if the original file was sparse > > > at all or maybe in different places. > > > > You've never run out of disk space as a result of a sparse file > > becoming non-sparse? > > So, are you arguing for or against tar converting files into sparse > files where it can as Daniel proposes? There is no arguing on that, since tar conversion is non-default, by -S option. > How does dump handle sparse files? dump handle them as sparse by default, no disk overflow. -- Andrey Chernov | http://ache.pp.ru/