Disk Utility: Extremely slow read phase during permissions repair
Shortly (but not immediately) after I upgraded from 10.3.9 to 10.5.6, repair permissions began taking a ridiculously long time to complete. Looking at the DU log, I see the read phase is the problem: DU spends over 2 hours on this, then performs the repair phase in a reasonable period. I'm using roughly 90 of my drive's 150 GB.
Last night, in Activity Monitor, I saw DU start 4 threads, which used 3-5% CPU initially. Checking later, I noticed CPU had dropped to 0% and stayed there until the repair phase started, at which point CPU went to 3-7%.
iMac G4 20" USB 2.0, 1.25 GHz 1.5/160 GB,
Mac OS X (10.5.7),
AE 5.7, AX 6.3, AE card 405.1 (all b/g)
Have you tried repairing your hard drive using Disk Utility? You may have some drive damage that's causing this. (You also could have some system problems, but that gets a little harder to troubleshoot, so start with the easy stuff.)
Also, although this does not address the problem, note that repairing permissions isn't something you need to be doing frequently. See:
Drive repair checked out ok. Took about 5 minutes.
I repair permissions each time I update OSX; otherwise, only if I suspect it's needed to solve a problem or, perhaps, I've updated a lot of apps. You're right that some people overdo it (not that it should ever hurt anything, though) and/or fret too much about seeing some of the same repairs being done each time, etc.
Repair Permissions is much slower in 10.5 than it was in 10.4 or 10.3. Nothing new here, this is normal (if annoying). It's faster from the command line (sudo diskutil repairpermissions /).
Still, RP really is almost
never necessary. So many threads here and concerns about people worrying about the treatment, when there's actually no symptom to cure! It's almost NEVER necessary, and there's so much silly lore around it (crud like "do it before and after every system update!" which is
totally unnecessary), it's almost become its own vortex of doom.
You know, don't you, that "Repair Permissions" doesn't actually REPAIR anything?
It does one thing: It goes through the BOM file (and, now with 10.5, the database as well), and compares the permissions on system files and on applications installed that put a receipt in there, and RESETS the permissions to whatever the BOM files and database say. Nothing more, nothing less. NO ISSUES related to the users home folder can be repaired in any way, because there are no receipts for them.
I'm not saying there aren't a set of very specific issues that "Repair Permissions" can't fix. But to say it should be regularly used to troubleshoot and as proactive maintenance is like recommending chiropractic care to fix a hangnail. It probably does more harm than good, as there may be cases where you actually WANT to change permissions, and "Repair Permissions" stomps all over them.
William Lloyd wrote:
Repair Permissions is much slower in 10.5 than it was in 10.4 or 10.3. Nothing new here, this is normal (if annoying).
A colleague did a check for me on his almost-identical eMac G4 and completed the entire process in < 30 minutes, twice. My system spends over 2 hours on the read phase alone. Further, as I said at the outset, I can see in my DU logs that the jump did
not coincide exactly with upgrading from 10.3.9 to 10.5.6.
As for the rest: Humbly request the debate move elsewhere.
I tried a bit of Unix I found in [this thread|http://discussions.apple.com/thread.jspa?messageID=6576238�]. It optimizes /Library/Receipts/db/a.receiptdb, which DU consults during repair, using the sqlite3 "vacuum" command.
The filesize was reduced somewhat and it appears the read phase improved as a result of the optimization: 1 hr 46 min vs. > 2 hours in all previous tests. The repair phase took 20 min, so that didn't improve (nor did I expect it to).
So it seems the vacuum trick can be worthwhile, but there's still a problem with my system that remains to be identified.
Leopard goes even further than TIger, in that not only are Access Control Lists available, they are enabled by default and actually used. It would appear that in addition to the normal POSIX permissions, going though the ACL entries of tens of thousands of system and application folders takes a while.
Yes, it's clear that repair is more thorough, and therefore takes longer, in 10.5 than before.
Nonetheless, my results are clearly anomalous, given that my colleague's eMac G4 (same processor & speed, comparable memory, nearly identical ATA drive, and comparable used/free space on the drive) consistently finishes the whole process in < 30 min. Comparing my results with his, it appears it's my read phase that's out of whack.
Just bringing in a little more data into this thread from another one I have been working on. My iMac G5 exhibited several strangenesses, not least a locked Time Machine disk and a refusal to load new programs, and in an attempt to put things right I did a 'Repair Permissions' using DU and it took MORE THAN FOUR DAYS. It was all ACLs, whatever that means. Anyway as you can guess, all I could conclude from this was that my machine (or rather the OS - since the disks had been checked) was very sick and I ended up re-loading Leopard from the install disks, doing all the updates, and erasing my TM disk, which so far (early days) seems to have fixed everything. All of which points to the idea that the slow permissions thing may be a symptom of something else, though what exactly was wrong I have not been able so far to find out.
This thread has been closed by the system or the community team.
You may vote for any posts you find helpful, or search the Community for additional answers.
Disk Utility: Extremely slow read phase during permissions repair
Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.