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: 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 | # ]