Date: Tue, 16 Nov 1999 13:29:03 -0800 (PST) From: Alfred Perlstein <bright@wintelcom.net> To: Julian Elischer <julian@whistle.com> Cc: Zhihui Zhang <zzhang@cs.binghamton.edu>, freebsd-fs@FreeBSD.ORG Subject: Re: On-the-fly defragmentation of FFS Message-ID: <Pine.BSF.4.05.9911161327080.12797-100000@fw.wintelcom.net> In-Reply-To: <Pine.BSF.4.10.9911161250040.25805-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Excellent point, however won't FFS's block placement strategy fix work around this unless the filesystem is already pretty full? Or is this one of the bad-case-scenarios for FFS? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9911161327080.12797-100000>