Moderators: jhartley, MSR734, nola
raattgift wrote:… all the .../.Spotlight-V100/ data was invalidated, so mds&mdworker fired up with a massive vengeance everywhere in parallel …
ilovezfs wrote:Thanks for the fast reply.
Due to your Spotled lighting experience, my plan is the following:
Before updating ...
1. mdutil -i off /Volumes/myzpool/mydataset0
2. Repeat step 1 for every data set, recursively
3. mdutil -E /Volumes/myzpool/mydataset0
4. Repeat step 3 for every data set
5. mdutil -i off /Volumes/myzpool on the root.
6. mdutil -E /Volumes/myzpool on the root
7. Manually delete all .Spotlight-V100 directories
8. Uncheck "Show child file system on the desktop and sidebar" in the ZEVO System Preferences Pane
9. Reboot
10. zpool export myzpool and unplug drives from the computer.
11. Reboot
Install the OS X 10.8.3 update & reboot
After updating...
1. Plug drives into computer.
2. Verify Spotlight has been enabled automatically on the root, mdutil -s /Volumes/myzpool
3. Let Spotlight finish with the root, monitoring the process "mds" in Activity Monitor (with "All Processes" showing)
4. Check "Show child file system on the desktop and sidebar" in ZEVO preferences
5. Reboot
5. Verify that Spotlight has been enabled automatically on each of the child data sets, mdutil -s /Volumes/myzpool/mydataset0
6. Let Spotlight work, monitoring mds in Activity Monitor and running sudo fs_usage -w -f filesys | less and eventually watching the time estimates, once they're available, shown when the Spotlight magnifying glass is clicked.
7. Reboot again.
8. Test spotlight works on the root and the data sets.
Results:
mds sat at 200% CPU for about 15 minutes and then Spotlight finished doing its thing and seems to work fine.
MelvinPhelps wrote:Hello friend were you were successful in your plan? I liked it very much so please post a suitable reply
Users browsing this forum: ilovezfs and 0 guests