![]() ![]() Eventually, in fact, once the largest free space fragments are down to less than 20 MB (not uncommon on a drive that has, say only 10% free space left) it begins to give up trying to defrag altogether. In fact the method it uses to defrag the smaller files actually increases the extent of free space fragmentation. It doesn't defrag larger files and it doesn't defrag the free space on the drive. It defrags files that are less than 20 MB in size. Some people will tell you that "OSX defrags your files anyway". Most users, as long as they leave plenty of free space available, and don't work regularly in situations where very large files are written and rewritten, are unlikely to notice the effects of fragmentation on either their files or on the drives free space much.Īs the drive fills the situations becomes progressively more significant, however. Whilst 'defragging' OS X is rarely necessary, Rod Hagen has produced this excellent analysis of the situation which is worth reading:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |