Michael Tsai on Twitter: "@danielpunkass After deleting the cache, I still had 60 GB of index files. Not sure why. It’s usually more like 9 GB for the whole folder."

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

Michael Tsai ‏@mjtsai Jan 10

Recurring problem since 10.11: in the morning, I'm down to 1.5 GB of free disk space. Over 100 GB not accounted for by OmniDiskSweeper.
2 retweets 2 likes
Michael Tsai ‏@mjtsai Jan 10

Not sure where the space is being used. Quitting apps doesn’t help, but it comes back after I restart.
1 like
Michael Tsai ‏@mjtsai Jan 10

Looks like the culprit is Spotlight. 2592 files in /.Spotlight-V100/Store-V2/6A539762-515B-41E7-80DC-AF1054850499/Cache/ up to 99 MB each.
2 retweets 5 likes
Michael Tsai ‏@mjtsai Jan 10

Just got the "Startup Disk Is Full" message, so back in a few after I restart.
Michael Tsai ‏@mjtsai Jan 10

The command I ended up using was "sudo du -mrd8 /.Spotlight-V100/|sort -n". After restart, still 60 GB of cache files, one that's 3.6 GB.
4 likes
Michael Tsai ‏@mjtsai Jan 10

Based on the contents of the txt files in the Spotlight cache, I think they were left by /System/Library/Spotlight/PDF.mdimporter
1 like
Michael Tsai ‏@mjtsai Jan 10

Tentative solution: exclude the folder with most of my PDFs from Spotlight and then reset it (sudo mdutil -E /).
3 likes
Daniel Jalkut ‏@danielpunkass Jan 10

@mjtsai Ugh, this kind of bug sucks. FWIW I just confirmed my whole .Spotlight-V100 "only" takes 6GB. (The volume that has my home folder).
1 like

‏@mjtsai

@danielpunkass After deleting the cache, I still had 60 GB of index files. Not sure why. It’s usually more like 9 GB for the whole folder.

7:38 AM - 10 Jan 2016

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.