OS X Leopard Bug Fixes: FileVault Breaks Spotlight

Apple's latest operating system, OS X 10.5 Leopard brings some pretty nice cutting edge technologies to the Mac. There are just a few, ah, Bleeding Edge, items on this yet to be fully polished software. I'm going to offer up a solution on what I did to correct and polish one of these rough edges.Bug Fix#1: FileVault Breaks SpotlightFirst thing I discovered after I did an Archive and Install of Leopard was that I couldn't search message bodies in Mail.app any more. Searching All Mailboxes in Entire Message gave me nothing. Doing a SpotLight search never resulted in any email message. Some quick web sleuthing on the Apple discussion forums turned up a number of folks with similar problems.However I also had an added twist. Searching in Spotlight also wouldn't turn up any of my contacts from Address Book. Not a one. While I could find files, applications, pictures, pdfs contents, etc all my old friends were gone from Spotlight. Luckily searching inside the Address Book worked just fine.I spent hours resetting Spotlight via terminal commands, tossing out hidden index files, rebuilding hidden index files, bouncing around the various troubleshooting haunts offered by Google and Apple and I still could not get Spotlight to fetch my information. Then I discovered that Spotlight was working just fine on my temporary backup computer. Bingo! My main Mac, a MacBook Pro has had FileVault running just beautifully for a while, when I upgraded I moved my sparseimage over to the computer and simply shut off FileVault. That was the difference. I was on to my solution.On further reading I discovered that a number of people have also had problems with Leopard upgrades breaking FileVault. I hadn't, or at least I thought I hadn't until now.The solution is pretty simple: If you have having my set of problems with Spotlight and you are running FileVault, 1. temporarily shut off FileVault. I can't be sure but I am guessing there is some kind of corruption going on with the indexing. So after you shut off FileVault... 2. force a rebuild of the Spotlight index (easiest way is to drag your home folder into the Privacy window of the Spotlight preferences, wait a minute for it to register, then remove it again to have Spotlight reindex). Allow your index to finish (read a book, have a coffee).3. Turn FileVault back on. Unfortunately you will have to allow Spotlight to reindex the, once again, encrypted, home folder.Hunch of what is going on under the hood: Overall one of Leopards key weaknesses is how it handles the upgrade process (how they every let it go out the door shutting off everyone's previously turned on FireWalls boggles my mind). I don't think it does a good job handling the upgrades of the FileVault sparseimage handling files (it should be converting them to the new sparsebundle format). During the final indexing I noted the DiskImagehelpe process working alongside the mds process. In all my previous force rebuilds of the indexes I hadn't seen this. I assume that, for some reason, though the index was being rebuilt correctly, there is some kind of encryption routine for the sparseimage that is supposed to be handled and it was not being called.Mabye, maybe not. I'm no engineer. I'll let a wiser soul fill in the blanks here...

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

#1 FileVault keeps another Spotlight Index

If you have FileVault with the new format in Leopard, the Spotlight index is located inside /Users, not under /Volumes. That's why reindexing the full hard drive does not work with FileVault user folders. You must also reindex the user folder. Take a look at: http://www.macosxhints.com/article.php?story=20071111175055549

#2 FileVault woes

I was using FileVault until complications with file open-with preference's not persisting between shut-downs. I've sinced turned it off, and have been noticing that Spotlight doesn't seem to be searching the contents of text-files as it once was. I'm in the process of rebuilding my index, which will hopefully resolve this. I'm guessing FileVault is somehow to blame.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Each email address will be obfuscated in a human readable fashion or (if JavaScript is enabled) replaced with a spamproof clickable link.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Enter the characters shown in the image.
By submitting this form, you accept the Mollom privacy policy.