The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
I recently downloaded the program Drive Genius from Apple.com's downloads section, hoping to find a program I can use to perform defrags on my computer. I got it installed and it seems to be working fine, but whenever I select my Macintosh HD in an attempt to defrag it, the defrag button becomes un-highlighted, and I can't click it.
Does this sound familiar to anyone? Got any suggestions or ideas?
[SIGPIC][/SIGPIC]
"For a few seconds Oskar saw through Eli's eyes. And what he saw was...himself. Only much better, more handsome, stronger than what he thought of himself. Seen with love."
--John Ajvide Lindqvist, Let the Right One In (Page 446).
HFS+, the default OS X filesystem, auto-defrags through normal usage. Unless you are trying to defragment a partition or hard drive with a different filesystem, don't bother.
[SIGPIC][/SIGPIC]
"For a few seconds Oskar saw through Eli's eyes. And what he saw was...himself. Only much better, more handsome, stronger than what he thought of himself. Seen with love."
--John Ajvide Lindqvist, Let the Right One In (Page 446).
HFS+, the default OS X filesystem, auto-defrags through normal usage. Unless you are trying to defragment a partition or hard drive with a different filesystem, don't bother.
I thought it only auto defragged =<20mb files as they were accessed. I also thought it was a function of the OS, not the files system. I really wish I could remember where I read this though. I've searched for the source a few times, but I haven't been able to find it again... I might have to do a few quick google searches...
HFS+, the default OS X filesystem, auto-defrags through normal usage. Unless you are trying to defragment a partition or hard drive with a different filesystem, don't bother.
I thought it only auto defragged =<20mb files as they were accessed. I also thought it was a function of the OS, not the files system. I really wish I could remember where I read this though. I've searched for the source a few times, but I haven't been able to find it again... I might have to do a few quick google searches...
Defragmentation on HFS+ volumes should not be necessary at all, or worthwhile, in most cases, because the system seems to do a very good job of avoiding/countering fragmentation.
It is risky to defragment anyway: What if there's a power glitch? What if the system crashes? What if the defragmenting tool has a bug? What if you inadvertently reboot? In some cases, you could make the situation worse by defragmenting.
This article is written by Amit Singh, who is pretty much the authority on the Mac OS X sub-system (apart from the developers that wrote it... but they're all under NDA).
Thanks for that Lewisham. I think you've found me some more bed time reading (I've got a small pile of documentation for various things, plus an ever growing folder of bookmarks to get through... there just isn't enough time).
I've finally found where I first read it though. It was John Siracusa's OSX 10.3 article (on page 5 for those of you playing at home). In the article, John links you to a forum thread containing a few more details about the whole process, and he was kind enough to post a nice little chunk of code from the darwin 7 source so that we could see just what happens. It's a great thread. There's a bit of discussion on hot file adaptive clustering too. I highly recommend reading it (unless you're not really into this stuff).
Edit:
Anyway, apologies to Zephonate for momentarily throwing things off topic.
It could be that it doesn't allow you do defragment the volume you're booting off. I'm pretty sure I could defrag HFS+ disks with the TechTool Protege (tech tool in a firewire thumb drive) at work.
Talking of HFS+, I wonder when Apple are going to pull their finger out in regards to going to a new filing system or updating it. HFS+ is beginning to get a bit long in the tooth now, there was rumblings a while ago about ZFS but that seems to have quietened down.
Also, since I appear to be on a minor file systems rant I wish Apple would also pull their finger out with other supported filesystems. I mean, how hard would it be for them to use FUSE or even take the work done by the macfuse guys and use that? I mean, OS X uses a load of opensource in it.
For example, by default Mac OS X can mount NTFS as read only and ftp servers as read only volumes (seriously, how hard would it be to add write support for ftp?).. now look at macfuse something I use on my Macbook Pro, i've got it set so it automatically mounts my windows bootcamp partition as read/write and I can mount ftp sites as read/write too. It's done totally transparently and works flawlessly. Apple should pull their finger out and get fuse into 10.6.
GrimReaper on
PSN | Steam
---
I've got a spare copy of Portal, if anyone wants it message me.
Posts
"For a few seconds Oskar saw through Eli's eyes. And what he saw was...himself. Only much better, more handsome, stronger than what he thought of himself. Seen with love."
--John Ajvide Lindqvist, Let the Right One In (Page 446).
I thought it only auto defragged =<20mb files as they were accessed. I also thought it was a function of the OS, not the files system. I really wish I could remember where I read this though. I've searched for the source a few times, but I haven't been able to find it again... I might have to do a few quick google searches...
http://www.kernelthread.com/mac/apme/fragmentation/ describes how Mac OS does it. The point is it doesn't defrag whole files, just large enough blocks that it keeps fragmentation under control.
This article is written by Amit Singh, who is pretty much the authority on the Mac OS X sub-system (apart from the developers that wrote it... but they're all under NDA).
I've finally found where I first read it though. It was John Siracusa's OSX 10.3 article (on page 5 for those of you playing at home). In the article, John links you to a forum thread containing a few more details about the whole process, and he was kind enough to post a nice little chunk of code from the darwin 7 source so that we could see just what happens. It's a great thread. There's a bit of discussion on hot file adaptive clustering too. I highly recommend reading it (unless you're not really into this stuff).
Edit:
Anyway, apologies to Zephonate for momentarily throwing things off topic.
It could be that it doesn't allow you do defragment the volume you're booting off. I'm pretty sure I could defrag HFS+ disks with the TechTool Protege (tech tool in a firewire thumb drive) at work.
Also, since I appear to be on a minor file systems rant I wish Apple would also pull their finger out with other supported filesystems. I mean, how hard would it be for them to use FUSE or even take the work done by the macfuse guys and use that? I mean, OS X uses a load of opensource in it.
For example, by default Mac OS X can mount NTFS as read only and ftp servers as read only volumes (seriously, how hard would it be to add write support for ftp?).. now look at macfuse something I use on my Macbook Pro, i've got it set so it automatically mounts my windows bootcamp partition as read/write and I can mount ftp sites as read/write too. It's done totally transparently and works flawlessly. Apple should pull their finger out and get fuse into 10.6.
---
I've got a spare copy of Portal, if anyone wants it message me.