From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 2 10:51:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E73D016A4E6 for ; Wed, 2 Aug 2006 10:51:05 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96BF543D45 for ; Wed, 2 Aug 2006 10:51:01 +0000 (GMT) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id k72Aovt25311 for ; Wed, 2 Aug 2006 20:50:58 +1000 (EST) Date: Wed, 2 Aug 2006 20:50:57 +1000 (EST) From: Dave Horsfall To: FreeBSD Hackers In-Reply-To: <20060802073340.GA713@turion.vk2pj.dyndns.org> Message-ID: References: <44CE199C.2020500@centtech.com> <17614.8289.134373.387558@bhuda.mired.org> <96b30c400607310847s1d2f845eo212b234d03f51e9a@mail.gmail.com> <17614.10982.499561.139268@bhuda.mired.org> <20060801072611.GA717@turion.vk2pj.dyndns.org> <20060801171150.GB3413@megan.kiwi-computer.com> <44CF8F1A.5090506@centtech.com> <20060801174048.GE3413@megan.kiwi-computer.com> <44D04797.1040201@freebsd.org> <20060802073340.GA713@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Aug 2006 10:51:06 -0000 On Wed, 2 Aug 2006, Peter Jeremy wrote: > As a general comment (not addressed to Tim): There _is_ a downside to > sparsifying files. If you take a sparse file and start filling in the > holes, the net result will be very badly fragmented and hence have very > poor sequential I/O performance. If you're never going to update a file > then making it sparse makes sense, if you will be updating it, you will > get better performance by making it non-sparse. Aha! Thanks for that, Peter. -- Dave, wondering why anyone would *not* want sparse files...