- FsSearch, which only searches file system attributes (names, etc)
- ReadWrite, which indexes content on the SAN the same way spotlight behaves for normal direct attached volumes.
SpotLightSearchLevel ReadWriteOnce enabled restart the service. While you shouldn’t, you may need to run mdutil (although you shouldn’t have to any more, but I’ve had to a couple of times) to get the spotlight indexing process kicked off. To do so run the mdutil command with the -E option, as you can see here (assuming a volume name of NAMEOFVOLUME):
mdutil -E /Volumes/NAMEOFVOLUMEYou can then check the status of the indexing process using the -s option with mdutil, as follows(assuming a volume name of NAMEOFVOLUME):
mdutil -s /Volumes/NAMEOFVOLUME
If for some arbitrary reason spotlight chooses not to index a folder (happens with Xsan in my experience), then you can use the mdimport command with the -f option:
mdimport -f /Volumes/NAMEOFVOLUME/MYPROJECTNAME
There will also be times when indices are built either using the wrong UID or where a failover during indexing causes corruption (my best educated guess as to why this happens). When it happens, simply RM the .Spotlight-V100 directory of the volume as you can see here:
rm -ri /Volumes/NAMEOFVOLUME/.Spotlight-V100
Also keep in mind that the same rules of what does not get indexed apply to Xsan volumes that apply to direct attached volumes. Namely, the following will be skipped:
- Hidden files (including those with names that contain leading periods).
- Invisible files (those using the kIsInvisibleFinder flag).
- Files that have been nested inside hidden or invisible folders.