4 ms·

Compound this issue with not being able to disable spotlight indexing of time machine backups on a NAS. Often I find mds is indexing for 4-6 hours at a time, us

Compound this issue with not being able to disable spotlight indexing of time machine backups on a NAS. Often I find mds is indexing for 4-6 hours at a time, using 20-40% cpu, with no way to stop or disable it (aside from disabling time machine). Its a real shame that Apple is allowing a growing list of paper cuts to fester on an otherwise pretty solid os (looking at you thunderbolt display kernel panics, unreliable external display support, etc).

xenophonf 5y ago
Runaway CPU utilization, kernel panics, unreliable displays, and network storage problems are _not_ the hallmarks of "an otherwise pretty solid os".
- LeSaucy 5y ago
  Care to mention any desktop os's that do not have these issues?
  - widowlark 5y ago
    no, they all have these problems and are all unreliable
DrBurrito 5y ago
so `mdutil -i off -d /Volumes/<mymountedNASvolume>`does not work for you?
- LeSaucy 5y ago
  Cool TIL about mdutil. I still cannot disable it as mdutil seems to be having trouble parsing the path to the share. Ive tried in bash/zsh/sh with all quoting/escaping patterns I can think of and I must be missing something. (shows up in in `mdutil -s -a`) /Volumes/Backups of Saucy's MacBook Pro: Indexing enabled. sudo mdutil -i off /Volumes/Backups\ of\ Saucy's\ MacBook\ Pro Error: could not resolve path `/Volumes/Backups of Saucy’s MacBook Pro'.
  - Volt 5y ago
    Escape the quote. Or just put the path in double quotes.