Spotlight may malfunction with future-creation-dates and if interrupted during initial index building. See note below. I've now decided 10.4.2 is a better bet than 10.4.1.
Jeff Hirsch
I can confirm that there are issues with Spotlight hogging the CPU under certain circumstances. In particular, the mds (metadata) process and mdimport process can eat up a huge chunk of available CPU and RAM. Upwards of 80% at times, causing a very noticeable slowdown on even the fastest of machines.
A quick search for "mds cpu" in the 10.4 Discussions over at Apple shows that a number of users are dealing with the same issue. Here is what I did to fix the problem and some thoughts on possible causes. First the fix:
1) Using the mdutil command-line utility in Terminal, turn off indexing for each of your drives. example:
$ sudo mdutil -i off /Volumes/your_hard_drive_name_1
$ sudo mdutil -i off /Volumes/your_hard_drive_name_2
2) Then use mdutil to remove the indexes from each drive
$ sudo mdutil -E /Volumes/your_hard_drive_name_1
$ sudo mdutil -E /Volumes/your_hard_drive_name_2
3) Physically remove the .Spotlight directories from the root of each drive.
$ cd /
$ sudo rm -fr .Spotlight-V100
(do the same for your second or third drive) BE CAREFUL WITH THAT RM COMMAND! One typo could ruin your day.
4) Use mdutil again to turn indexing back on for each drive
$ sudo mdutil -i on /Volumes/your_hard_drive_name_1
$ sudo mdutil -i on /Volumes/your_hard_drive_name_2
5) Spotlight will now re-index all drives and should behave in a normal fashion. (No longer uses 60%-80% of your CPU)
Finally a couple of quick thoughts on possible causes:
1. My initial indexing process after installing Tiger was interrupted by a couple of reboots I had to do while installing third-party apps. This may have left me with a funky index when Spotlight tried to pick up where it had left off. I suggest letting it fully index your drives before rebooting the machine at all.
2. A few users in the Discussions over at Apple noticed that they had files on their hard drive with modification dates AFTER the current date. i.e. days/months/weeks into the future. These files may have been causing Spotlight to choke as it tried to make sense of a date that hadn't happened yet.
I did a quick search for files modified "after" today and found a handful of them on my hard drive. (A few were dated 2031!) I used the touch command in Terminal to give these proper dates. If you have a lot of these files, you might want to create and Automator script to touch them all for you.
Hope this saves some of you a headache or two.
No comments:
Post a Comment