|
|
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 |
|