10.10.3 Finder Status Bar information is wrong, TB not GB

i have a similar issue... since i've updated to 10.10.3 I get this bad disk information... i'll show you in the following images... there you can see how the mac is saying that i'm only left with 96 gb of my 500 gb disk... while the truth is I have at least 330 gb of free space.

i've allready runed the disk utility from boot... and it shows some issues with the block count for some files... once it ends, it gives me some gb back... but there's still a lot of space to recover.

I'm using a macbook pro retina display mid 2012.

if someone has a solution please post it!

I Installed the upgrade immediately and had no issues until tonight, when the computer gods gifted me 3.1PB available disk space on my 500GB HD. correct disk space shows up elsewhere. Ran repair HD in Disk Utility via the Recovery HD. Disk Utility found and corrected numerous block issues that were gone (as we're all issues) on the second run. Permissions are fine. My sense of order is not.

FWIW, while I migrated iPhoto to Photos after the install, tonight was the first time I played around with Photos.

Has anyone tried a reinstall of Yosemite? I may resort to that come morning.

THanks for this thread. I thought I was going insane.

I have exactly the same issue with my 2008 MacBook Pro. I tried disabling Time Machine and restarting as suggested and found, as others have, the correct values are shown for a while before the problem recurs. I haven't tried any other suggestions as I'm hoping a fix from Apple will follow before too much longer. I'm sure if the problem had been encountered by more people there would be more than two pages of comments in response to mculmore's original post, and I'm wondering what we who are experiencing this problem might have in common. I'm pleased that most of you have much more recent Macs than my own - which discounts age, but are you using OS X in languages other than English? (mine is in French) Are you running HD or SSD? Original Apple or 3rd Party upgrade? (I've upgraded mine with a Crucial MX100 SSD)

Thanks

Same problem here.

What seems to have done the trick for me it's to disable "Time Machine".

I've had it turned off for some days and the correct space is still displayed.

This is not really a systemic fix since I definitely want to have "Time Machine" enabled, but it might point to where the problem is lying.

cheers

I also turned Time Machine off and, within minutes, the hard drive adjusted itself to what seems to be the correct amount of free space. I turned Time Machine back on and rebooted, and the correct figure has remained static. I'll see how long it lasts and keep my eyes out for anything that might trigger a relapse.

When the Time Machine toggle worked, it set my mind on what might link time machine with this particular issue. I don't have enough information to even propose a hypothesis, but it may be worth noting that I was trying to empty the trash last night. I had a ton of files in there; many did not want to delete; and I had to restart the finder several times and repeat the procedure several times to finally delete everything. At one point, I noticed that Time Machine was performing a back up during this blusterduck. I don't know enough about how the little elves who live inside my MBP to speculate on how these two things might be connected, but that's the only visible role that Time Machine could have played in creating this situation (for me).

I'm using German OS X Yosemite, SSD, Original Apple

Same problem here, turned off TM and finder reported proper SSD info.

This looks like a bug to me, hopefully Apples will patch it with next update.

I found some information for this problem.

I think this issue is bound to 'Local Snapshot'.

About this feature, you'll find some help from : About Time Machine local snapshots - Apple Support

If it was from this feature, then simply turn off to resovle it.

How to Delete the Local Backups

http://www.howtogeek.com/212207/how-to-free-up-space-used-by-time-machines-local -backups-on-your-mac/

I hope it will work.

Thanks Finethanq for shedding some light on this.

Nevertheless this seems to be a bug to me of the new update, which I hope gets sorted out.

It's good that users managed to pinpoint the location of the problem, I hope apple soon manages to release a patch to fix this so that users don't have the need to go and disable local snapshots of TimeMachine.

Same problem here. 😠