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: smkolins on Mar 05, '03 08:29:08AM

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.

See man tunefs.

---
= - - -- - - - =
Steven
smkolins@mac.com
http://homepage.mac.com/smkolins
Possess a pure, kindly, and radiant heart!



[ Reply to This | # ]
A possible fix for 'overlapped extent allocation' errors
Authored by: lamon on Mar 05, '03 08:45:43AM

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.

I can't check here at work but is tunefs relevant to HFS+? I throught it to be a FreeBSD/UFS manpage.



[ Reply to This | # ]
A possible fix for 'overlapped extent allocation' errors
Authored by: smkolins on Mar 06, '03 10:16:06PM

Perhaps. I'm seeing lot's of references to bunches of OSes - linux, BSD, HPAUX... I'm seeing references to hfs modifications....

Nothing direct yet, but I know the command iostat wasn't enabled correctly in 10.0 or 10.1 but it works in 10.2....

tunefs might be there but not exactly reachable....

---
= - - -- - - - =
Steven
smkolins@mac.com
http://homepage.mac.com/smkolins
Possess a pure, kindly, and radiant heart!



[ Reply to This | # ]