From owner-freebsd-fs Tue Nov 16 13: 9:33 1999 Delivered-To: freebsd-fs@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 22C3C14D98 for ; Tue, 16 Nov 1999 13:09:30 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id QAA09240; Tue, 16 Nov 1999 16:09:25 -0500 (EST) Date: Tue, 16 Nov 1999 14:56:56 -0500 (EST) From: Zhihui Zhang To: Julian Elischer Cc: Alfred Perlstein , freebsd-fs@FreeBSD.ORG Subject: Re: On-the-fly defragmentation of FFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 16 Nov 1999, Julian Elischer wrote: > > > > I think you're missing an obvious point, as the file is written out > > the only place where it is likely to be fragmented is the end, hence > > the reason for only defragging the end of the file. :) > > usually, though database files can be written randomly as they are filled > in. > Can a database file has holes? I had some experience with Oracle. I used to create a large file for a database and assumed that all space of the database file are pre-allocated. Otherwise, the performance of the database will be poor. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message