Posted on 12-17-2014 07:11 AM
Has anyone encounter the issue with 10.9 reporting/showing incorrect disk space remaining?
Background--
Early 2014 Macbook Air 11" 128GB HD. Shared student device.
Students were logging in and chewing up the storage space. Found a script that runs at login to delete any non local accounts older then 7 days. Issue that I'm having is, storage space is being reported incorrect. I have checked on the laptop (hidden and non hidden folders) and there is no way that it would add up to around 100GB of data.
Solved! Go to Solution.
Posted on 12-17-2014 07:15 AM
Sure you're not running into this annoying 10.9 bug? have you actually done a get info on the HD?
https://jamfnation.jamfsoftware.com/discussion.html?id=10555#respond
Posted on 12-17-2014 07:15 AM
Sure you're not running into this annoying 10.9 bug? have you actually done a get info on the HD?
https://jamfnation.jamfsoftware.com/discussion.html?id=10555#respond
Posted on 12-17-2014 07:40 AM
I'm getting the info from the laptop itself. I saw one of your post on that thread, Let me try try running this on a few laptops.
find /var/folders -name "*.iscachebmp" -type f -exec rm -v "{}" ;
Posted on 12-17-2014 08:54 AM
Another thing to try is to force Spotlight to rebuild.
Often that is the cause of the discrepancy being reported in disk space utilities.
Posted on 12-18-2014 06:06 AM
@CasperSally You're were correct. It was the cache files filling up. I have a smart group and a policy that runs a script. Its been working great! Thank you!
@boettchs I have tried that first but found out that it takes awhile before re-indexing is completed. Students aren't logged in long enough to complete. But the solution Caspersally mentioned worked.
Posted on 12-18-2014 06:11 AM
@Johnny.Kim - good you got a solution. Indexing is indeed a slow process - especially if there's a lot of data on the Mac. Glad you got it sorted.
Posted on 05-07-2015 06:52 AM
beware if you're running find /var/folders -name "*.iscachebmp" -type f -exec rm -v "{}" ; as an execute command on a policy, which worked for me in 9.32, appears broke in 9.65. Running it as a script instead works.