Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A possible fix for 'overlapped extent allocation' errors' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A possible fix for 'overlapped extent allocation' errors
Authored by: karmaworld on Mar 04, '03 10:12:21AM

I too encountered this error and was unable to fix by fsck. I came across a post in Apple discussions where someone suggested running OS9 disc repair utility. Since I have been "classic free" for some time now, I booted up from my OS 9.2.2 cd, ran Disc repair from the CD and voila, problem solved with no ill effects on my G4 933. It has been about a month now.

---
With kindest regards,
Laurence



[ Reply to This | # ]
A possible fix for 'overlapped extent allocation' errors
Authored by: revcosmo on Mar 04, '03 03:18:22PM

To become "classic free" did you simply delete the OS 9 System Folder, or was there more to it than that?



[ Reply to This | # ]
A possible fix for 'overlapped extent allocation' errors
Authored by: tlassiter on Mar 04, '03 05:53:10PM

I have experienced this problem at least a half-dozen times since June
2002 with a PowerBook G3/400. At first I blamed flakey RAM and
replaced it with guaranteed RAM. A larger (and needed) hard drive made
no difference. Neither did upgrading to Jaguar 10.2.3. Last week I had
another occurrence that Disk Warrior could not repair. fsck kept finding
overlapped files. Rather than wipe the drive (again), I reinstalled the OS
with the Archive and Save option. Other than having to reset everything
and losing my User file and docs, the PowerBook seems OK again. But I
don't trust it with critical files.

If this problem were to occur with the desktop system that pays my bills,
I would be sunk. Until OS X learns to behave, I can't trust it and won't
convert the machines that I depend on for my livelihood.



[ Reply to This | # ]
A possible fix for 'overlapped extent allocation' errors
Authored by: osx_4me on Mar 05, '03 11:32:59AM

I have used 10.2 on numerous machines, without ever having any 'overlapped extent allocation' errors. And I use fsck more often than I really need to.
I'm sorry you're having problems, but it's wrong to blame this on OS X. Sorry.



[ Reply to This | # ]
It is more likely an HFS/HFS+ file system bug
Authored by: jollyroger on Apr 04, '03 08:10:09AM

If your hard drive ever reached the point of being over 85%-90% full, then it is likely that the HFS file system caused the extents tree to be overwritten (overlapped) because the B-Tree portion of the directory itself was out of space!

Take a look at the comments in this MacFixit forum:

<http://www.macfixitforums.com/php/showflat.php?Cat=&Board=Forum8&Number=435249&Forum=All_Forums&Words=&Match=Entire%20Phrase&Searchpage=0&Limit=25&Old=1day&Main=435138&Search=true>

Pay attention to MacWizard's comments (he is/was on the TechTool team). Some quotes:

" HFS+ does a much better job of keeping track of files that have many pieces (extents). If an HFS disk is heavily fragmented and more than 70% full, irreparable damage can take place to the Extents B-Tree portion of the disk directory if any more files are added. The corresponding limit for HFS+ disks is 85%."

and

"If the disk is more than 85% full, and is sufficiently fragmented (something I cannot precisely define), the Extents B-Tree is in danger of irreparable damage. When new entries need to be written in the Extents B-Tree, older ones are simply overwritten. The developer of TechTool Pro has reproduced this problem in a lab setting.

The Extents B-Tree keeps track of file extents (pieces) beyond the first three extents of each file (those are recorded in the Catalog B-Tree.) Within Apple, the Extents B-Tree is called the Extents Overflow file. The name alone suggests a potential problem. I suggest you archive some of the data as soon as possible.

I have screenshots of disks that have zero free bytes and still work, but they were not heavily fragmented. "

I'm not sure I can remember where or when, but at some point, years ago, I learned that you should never fill a Mac HD more than 90% or you will have problems. Since then I have only let my hard drives get 90% full on occasion. And I do seem to have much fewer directory-related hard drive problems than other Mac users.



[ Reply to This | # ]