From owner-freebsd-questions@FreeBSD.ORG Tue Aug 16 13:45:51 2005 Return-Path: X-Original-To: questions@freebsd.org 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 B637416A41F for ; Tue, 16 Aug 2005 13:45:51 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail25.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A05743D45 for ; Tue, 16 Aug 2005 13:45:51 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 15405 invoked from network); 16 Aug 2005 13:45:50 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail25.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 16 Aug 2005 13:45:50 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id AC18837; Tue, 16 Aug 2005 09:45:49 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Lei Sun References: <200508151320.j7FDKCVq025507@clunix.cl.msu.edu> <20050815203917.GA75533@xor.obsecurity.org> From: Lowell Gilbert Date: 16 Aug 2005 09:45:49 -0400 In-Reply-To: Message-ID: <44d5oeov02.fsf@be-well.ilk.org> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: questions@freebsd.org Subject: Re: disk fragmentation, <0%? 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: Tue, 16 Aug 2005 13:45:51 -0000 Don't top-post, please. Lei Sun writes: > Then, my other question is, > > If the file space allocation works like Glenn said earlier, how come > with the exact same files from 2 different installations using the > exact procedures, can result in different fragmentation? > > in the atacontrol raid1 failure case, /dev/ar0s1a: ... 0.5% fragmentation > in the new build case, /dev/ar0s1a: ... 0.0% fragmentation > > That doesn't seems to make a lot of sense. There are lots of possible explanations, including (non-harmful) race conditions. Is there some reason you care?