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: tjamison on Apr 28, '03 06:03:17PM

I have been having this problem with a G3 Imac and thought I
was alone. I had the problem, reinstalled OSX and things
seemed fine, then all of a sudden stuff stopped working (many
apps) and progressively got worse until finder wouldn't start. I
went to the OSX install disk and ran disk utility, only to find
hundreds of OEA errors. Decided to wipe the volume clean. Did
an Erase (using the Erase tab) and reran repair on the erased
volume 3 times in a row. 1st time got a minor error - repaired.
2nd time it looked clean. 3rd time got 1 OEA error. What's
going on here?



[ Reply to This | # ]
A possible fix for 'overlapped extent allocation' errors
Authored by: heynnema on Apr 28, '03 08:13:19PM

I have the same kinds of errors. Nothing I could do would get rid of
them. I got used to booting into single user mode and running fsck all
the time...

then I disabled all of the Symantec/Norton startupitems and extensions,
and guess what?!? ALL OF THESE EXTENT ERRORS WERE GONE, AND
I'VE NEVER SEEN THEM AGAIN!!!!

AND... my USB floppy disk drive no longer complains when I try to eject
a floppy disk with a "this disk is in use" error message. It now ejects the
FIRST time, without error, instead of always requiring TWO eject
commands to make it happen!!!

Symantec/Norton stuff has ALWAYS been bad news, even in OS 9!



[ Reply to This | # ]