From owner-freebsd-questions@FreeBSD.ORG Thu Aug 28 13:21:31 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0853106567D for ; Thu, 28 Aug 2008 13:21:31 +0000 (UTC) (envelope-from fbsd06+ZH=f1c166d5@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id BAB6B8FC2A for ; Thu, 28 Aug 2008 13:21:31 +0000 (UTC) (envelope-from fbsd06+ZH=f1c166d5@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 50BCD23E402 for ; Thu, 28 Aug 2008 09:21:30 -0400 (EDT) Date: Thu, 28 Aug 2008 14:21:26 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080828142126.7ffa3b1d@gumby.homeunix.com.> In-Reply-To: <20080828133712.H64545@wojtek.tensor.gdynia.pl> References: <20080828080935.9D7044FC901@xroff.net> <20080828133712.H64545@wojtek.tensor.gdynia.pl> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: defrag X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 13:21:32 -0000 > On Thu, 28 Aug 2008 10:13:40 +0200 > Eduardo Morras wrote: > > > No, if you check a NTFS disk after some work, it's heavily > > fragmented. As you fill it and work with it, it becomes more and > > more fragmented. How did you measure it? AFAIK the percentage fragmentation figures given by windows tools and fsck, aren't measured on the same basis. On Thu, 28 Aug 2008 13:41:22 +0200 (CEST) Wojciech Puchar wrote: > it's just like FAT, because nothing is done to prevent fragmentation. > > if NTFS needs to allocate block, it simply get first free. > > consider writing to 3 files, one block at a time to each. > > you will get block arranged like this (where 1 is file 1's data,2 is > data from file 2 and 3 from file 3): > > 123123123123123123123123213213 This is just untrue. I don't much like Microsoft, but I don't think there's much to be gained by out-fudding them.