|
|
A possible fix for 'overlapped extent allocation' errors
i'm kinda mad...long story short, i had an OEA and when i called apple, they said that the only way to fix it was to wipe the hard drive and reinstall OS X - and this was from an senior tech. if this works, consider my faith in the apple tech help severely damaged.
A possible fix for 'overlapped extent allocation' errors
If it works, I'm mad too. I just had to go through that whole rigamarole -- neither Disk First Aid (on the OS X disks) nor Drive10 couldn't repair it. I wiped and reinstalled -- and spent two full days doing it. Sigh.
A possible fix for 'overlapped extent allocation' errors
I don't see why you'd get mad at them. They're not there to go kernel-hacking for you, just explain how to get iTunes to stream. Technical support is granny-support, not power-user support. Power-user support is called "consulting." :)
A possible fix for 'overlapped extent allocation' errors
AMEN !
A possible fix for 'overlapped extent allocation' errors
It won't always work. Sometimes those overlapped files are core system files. The best overall fix is to nuke and reinstall.
A possible fix for 'overlapped extent allocation' errors
I agree. There is actually nothing new here. If you happen to know or figure out what's crosslinked you could always delete just those parts and ussually recover pretty gracefully. Figuring out what's crosslinked may be hard. In this case he just guessed and guessed correctly.
A possible fix for 'overlapped extent allocation' errors
Would turning on journaling help Disk Utility and/or fsck in fixing these problems?
Just a thought ;)
---
A possible fix for 'overlapped extent allocation' errors
Interesting thought....
A possible fix for 'overlapped extent allocation' errors
I have had my harddisk journaled since 10.2.3, but the number of the overlapped extents had gone up since then. There used to be about 4, now there are 10!
A possible fix for 'overlapped extent allocation' errors
From what I know, HFS+ is fragile when the disk is filling up too much. You do not risk this problem unless you go over 85% occupation of the disk (note that UFS on Unix usually reserve 10%). The main cause I have seen for this is usually the swap file growing up and filling the partition (could also be a runnaway log) and a lot of other problems are due to this, like corrupted or diseappearing preference files.
A possible fix for 'overlapped extent allocation' errors
I agree about the problems of filing the hd, and while it could be because of the swap file(s) I think it's more likely that the system will go nuts trying to find unfragmented space (or actually give up) and fragmentation on the most recent files will go through the roof.
A possible fix for 'overlapped extent allocation' errors
True. But usually, the system fails to find space because the HD is full, and I think that one of the main causes of accidental fill-up is a runaway swap. If you keep 85% free, you should have no problem. I have been up to 95% on an archive partition (large files only) without problems either.
A possible fix for 'overlapped extent allocation' errors
Perhaps. I'm seeing lot's of references to bunches of OSes - linux, BSD, HPAUX... I'm seeing references to hfs modifications....
A possible fix for 'overlapped extent allocation' errors
I suffered the dreaded OEA error when my HD was only |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.14 seconds |
|