Well here is what I've found right now.
I changed now ALL mdimporters (system/library/spotlight)
from 10.7.5 to 10.6.8. What can I say: right now the
new index takes 45 minutes. And this is NO JOKE.
BUT PLEASE WAIT to do it too. I will proof it again.
These are the md's
FWIW, comparing those files between 10.7.4 (which doesn't seem to have a problem) and 10.7.5 shows different versions for only three files with 10.7.4 first:
CoreMedia.mdimporter 0.705.78 0.705.94
Mail.mdimporter 5.2 5.3
vCard.mdimporter 2.4 2.5
Needless to say, all of the 10.6.8 components have earlier versions than 10.7.4, except MIDI.mdimporter, which has an earlier version but a later modified date.
I disabled Time Machine when I first had the issue and the performance 'seemed' to have returned to normal, I am not convinced after a week's use. Time Machine is slow as well.
We should keep digging though, as something may appear. In the meantime, I will keep submitting feedback to Apple in an official manner.
I watched in fascination as the predicted time of a 150gb backup was up to 22,000 days and counting.
My machine had previously suspended early into the beginning of a first backup and then timemachine appeared to stall.
After cancelling and starting again the problems started.
Deleting the folder on the timemachine backup drive solved the problem,
Have you disabled Spotlight using the following command?
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
Your backups should return to normal.
When Apple sort this out, use the following command to re-enable Spotlight;
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
Faced with one of two options really (downgrade to 10.7.4 or upgrade to ML) I decided to give ML a chance.
Under 10.7.5 SL indicated that it would take 14 days to re-index my MBA hard-disk (after diabeling it to allow TM, and re-enabeling it).
So I did this:
1) Backup my entire drive using Carbon Copy Cloner (just in case) ~ 1 hr.
2) Verified my disk using Disk Utillities (always do it before new system installation).
3) Installed ML, 10.8.1 (45 minutes).
4) Enable TM. It took about 3 hrs to update about 22 Gbytes data. Simultaneously with TM backup SL takes about 7 hours for a complete new reindexing.
Everything seems to be back to normal and the times are more or less as they were prior to 10.7.5 (finally).
>So if your machine is compatible with ML, this is one option to consider.
And YES, Apple should release a fix to this bug in 10.7.6, and FAST.
Amit Meller wrote:
Faced with one of two options really (downgrade to 10.7.4 or upgrade to ML) I decided to give ML a chance...
...3) Installed ML, 10.8.1 (45 minutes)...
Where did you get 10.8.1? 10.8.2 is the current version and what's offered on the App Store now. The Mountain Lion forum has its own tales of woe associated with the upgrade to 10.8.2 so it sounds like you got lucky.
Just spoke with apple too - they recommended downgrade to 10.7.4, said engineers are working on it, also suggested I submit a report to feedback:
Maybe if we all do this, they'll get it fixed more quickly!
J Scott Coatsworth wrote:
Yes - they said to restart, holding down the option key, to put the computer in recovery mode. Then click on restore from time machine. I haven't tried it yet, and obviously want to only restore the operating system. But that's what they said.
That's the Catch-22. You can restore your computer using Time Machine to an earlier state when 10.7.4 was its OS, but that's your whole computer, not just your operating system. And if you ran the 10.7.5 update when it was first released, all the changes (probably quite a few) since then won't be present. You can then go back to more recent TM backups to restore the succeeding changes piecemeal but that might take a while. And if your TM backups aren't for the entire HD, I'm not sure how what's not been backed up but is currently on your HD is handled. For example, TM isn't reliable for virtual machine backups, which can get pretty big, so I exclude them from the TM backup. Would the current VM's still be on the HD after a restore from an earlier time? I don't know because I'm not clear if the Recovery process wipes the boot partition clean before the restore begins.