-
All replies
-
Helpful answers
-
Feb 19, 2015 1:55 PM in response to JeffShipmanby Mathieu Mauser,Did your volume failover? Is another controller hosting it?
What you have done to resolve this? Have you tried mdfind to see if it lists results from your SAN volume?
-
Feb 25, 2015 9:48 AM in response to Mathieu Mauserby JeffShipman,The current attempts are as follows:
I removed the clients from the Xsan, and left one of two mdc up.
I ran repair disk permissions on the boot drive
I disable spotlight on the volume fron the Xsan admin
In the terminal window, I ran the following: sudo rm -rf /Volumes/[VolumeName]/.Spotlight-V100
in the terminal window, I ran the following: sudo cvfsck -wv [VolumeName]
I re-enable the spotlight on the volume fron the Xsan admin
After four days it is still showing estimating indexing in the spotlight menu.
This is a 40tb RAID Promise with 17tb free
-
Feb 26, 2015 5:30 PM in response to JeffShipmanby Claudio Sanchez1,Try unmounting and remounting on the active MDC. Wait a few minutes. Check output of "mdutil -asv". Note the volume must be mounted on the active MDC for indexing to occur. A client must mount the volume after Spotlight is enabled. Note that "client" also applies to the active MDC when it is doing the indexing.
These are old but contain relevant information:
Xsan 2: Spotlight may take an unusually long time to index Xsan volumes - Apple Support
-
Feb 27, 2015 4:24 AM in response to Claudio Sanchez1by JeffShipman,What is the importance of "Note that "client" also applies to the active MDC when it is doing the indexing."?
-
-
Feb 27, 2015 11:28 AM in response to Claudio Sanchez1by JeffShipman,So if I left a MDC as a client of the SAN during the indexing the indexing may failed?
-
Feb 27, 2015 11:35 AM in response to JeffShipmanby Claudio Sanchez1,The active MDC does the indexing. It's not the fsm process that runs the volume that does the indexing, but rather Spotlight related processes (mds, mdworking, mdimport, etc) which are accessing files on the volume which the MDC has mounted as an Xsan client. The volume has to be mounted on the active MDC for indexing to work. The mount has to occur after Spotlight has been enabled on the volume.
As stated in this article:
"Use Xsan Admin to unmount and remount the volume on the controller that is currently hosting the volume. It may still take several minutes for Spotlight to activate."
You could also do this on the MDC (which you would have to do if it's a Yosemite MDC):
sudo xsanctl unmount VolumeName
sudo xsanctl mount VolumeName