On Dec 3, 2003, at 6:02 PM, Loren Schooley wrote: > When you use disk utility to format normally, it leaves what you might > call a ~table of contents~, or cache, of every fragment of the disk > that ever had a file. If you leave it that way when you install, well, > every time your CPU looks for data, it has to read all the historical > contents of the old systems to find out it isn't there anymore. The file system drivers in the Mach kernel use a high degree of volume fragmentation by default to combat file fragmentation. The reasons you cite date back to OS 9 filesystem drivers, and do not apply to OS X. Even if you create and delete large amounts of files in an attempt to fragment the file system, the disk read/write time will be only minimally effected, and will recover from the fragmentation quite quickly as new data overwrites blocks where old data is stored. Since the HFS+ journaling filesystem drivers only journal the disk's metadata, there's very minimal, if any at all, slowdown in system performance with OS X's journaled filesystem. -- Chris