Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Omni Disksweeper size does not equal what Mac says

N

NukeIT

macrumors regular
Original poster
Mar 20, 2013
233
0
So I noticed today that my rMBP early 2013 512GB SSD was reporting an abnormally small amount of free space ~60GB. Wondering what was taking up space ran Omni it only reports ~250GB being used. Figured I may have some corruption ran Disk Utility, and it found Orphaned Blocks and was not able to calculate free space. Booted to recovery to repair drive and it failed to repair. So booted to my bootable USB and ran disk Utility again and repair was successively. Rebooted to normal boot disk ran Disk Utility again Drive is okay and repaired permissions.

Now showing ~110 GB free while Omni shows ~250 GB free.

Any idea why the two would be so far off??
 
NukeIT said:
So I noticed today that my rMBP early 2013 512GB SSD was reporting an abnormally small amount of free space ~60GB. Wondering what was taking up space ran Omni it only reports ~250GB being used. Figured I may have some corruption ran Disk Utility, and it found Orphaned Blocks and was not able to calculate free space. Booted to recovery to repair drive and it failed to repair. So booted to my bootable USB and ran disk Utility again and repair was successively. Rebooted to normal boot disk ran Disk Utility again Drive is okay and repaired permissions.

Now showing ~110 GB free while Omni shows ~250 GB free.

Any idea why the two would be so far off??
Click to expand...

Because Omni does not show (or count) a lot of hidden and system files.

Do you happen to have Time Machine turned on. Time Machines local snapshots can take up some space.

Enter the command below in Terminal and it will list all base folders and their size. Post the output of the command if you want some help deciphering.

Code: 
sudo du -d 1 -x -c -g /
 
Weaselboy said:
Because Omni does not show (or count) a lot of hidden and system files.

Do you happen to have Time Machine turned on. Time Machines local snapshots can take up some space.

Enter the command below in Terminal and it will list all base folders and their size. Post the output of the command if you want some help deciphering.

Code: 
sudo du -d 1 -x -c -g /
Click to expand...

Will have to run Terminal code tomorrow when I get home.

I wasn't aware Omni didn't account for hidden files, for some reason I thought I read that it accounted for everything. Even tho in this case 120 GB of hidden/system files seems extreme.

I do have Timemachine enabled.

I figured there is always some discrepancy, ~10-15 GB tho would be on the high side I would think. Not 120 GB

Will get back with you tomorrow when I have had time to mess with it more.

Cheers.
 
Weasel boy thanks again.

The files were in ".mobilebackups.trash".

Took a bit of wrangling to get them to fully delete and once I did had an additional ~150 Gigs of available storage. Also noticed the the "other" catagory is now back to a more normal accepatable size.
 
NukeIT said:
Weasel boy thanks again.

The files were in ".mobilebackups.trash".

Took a bit of wrangling to get them to fully delete and once I did had an additional ~150 Gigs of available storage. Also noticed the the "other" catagory is now back to a more normal accepatable size.
Click to expand...

Yeah... I had the same thing happen to me once. What happens is when you delete files with Time Machine on they go to /.Mobilebackups and get deleted when your disk reaches 80% full. Or they get deleted if you briefly turn off Time Machine. When they get deleted from /.Mobilebackups they go to that /.mobilebackups.trash folder you found for a short time while the OS deletes them. For some reason they sometimes get stuck there. Mine was because of some Crashplan app files that were stuck there. I had to jump through all kinds of hoops to get mine deleted also.

Do you happen to use Crashplan?? I helped another user with this exact issue a couple months ago, and he was using Crashplan also.
 
Weaselboy said:
Yeah... I had the same thing happen to me once. What happens is when you delete files with Time Machine on they go to /.Mobilebackups and get deleted when your disk reaches 80% full. Or they get deleted if you briefly turn off Time Machine. When they get deleted from /.Mobilebackups they go to that /.mobilebackups.trash folder you found for a short time while the OS deletes them. For some reason they sometimes get stuck there. Mine was because of some Crashplan app files that were stuck there. I had to jump through all kinds of hoops to get mine deleted also.

Do you happen to use Crashplan?? I helped another user with this exact issue a couple months ago, and he was using Crashplan also.
Click to expand...

There were almost 400,000 files to delete at first. Most of them deleted just fine, however the Crashplan ones were the troublesome ones.

Even after crashplan was shutdown, it still would say they were in use. Ended up using "Trash It" to get rid if them. Command line wouldn't even delete them.
 
Weaselboy said:
Because Omni does not show (or count) a lot of hidden and system files.[/CODE]
Click to expand...
I've never had an issue with Disksweeper not counting hidden files. Please expound on this. I see it counting /tmp, /etc and /Volumes as an example.

Edit: a quick compare shows both du and omnidisksweeper accounting for the space on my mac mini
 
Last edited:
maflynn said:
I've never had an issue with Disksweeper not counting hidden files. Please expound on this. I see it counting /tmp, /etc and /Volumes as an example.

Edit: a quick compare shows both du and omnidisksweeper accounting for the space on my mac mini
Click to expand...

Test it now yourself and you will see what I am talking about. I just did this back to back on my system. ODS and Terminal output below.

Notice the Terminal du command shows 179MB in /.DocumentRevisions-V100 and 271MB in /.Spotlight-V100 and ODS shows zero in those folders. Same with 5MB in /.fseventsd.

I have Time Machine's local backups turned off, so they don't show up, but if I had that enabled it would show under the du command and not show in ODS. Same with the /.Mobilebackups.trash folder that was causing the problem in this thread. I have tested this repeatedly.

Look at user Logo123's posts #5, #8, and #10 in this thread. He has 2GB in /.MobileBackups and 62GB in /.MobileBackups.trash that does not show at all in ODS.

The issue is ODW does not have rights to those hidden folders, so it can't check them for content. You can get around this by running ODS with sudo, and then it will show the hidden folder content, but when run normally it does not. Se my post #16 from Logo123's thread I linked above.

Code: 
sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper

VX16xGO.png


Code: 
xx-Macbook:~ xx$ sudo du -d 1 -x -c -m /
179	/.DocumentRevisions-V100
5	/.fseventsd
0	/.PKInstallSandboxManager
271	/.Spotlight-V100
0	/.Trashes
0	/.vol
8547	/Applications
3	/bin
0	/cores
1	/dev
1	/home
8054	/Library
1	/net
0	/Network
5274	/private
2	/sbin
7008	/System
24290	/Users
457	/usr
1	/Volumes
54092	/
54092	total
 
I see where you're getting at, stuff like the .spotlight folder. I never noticed that, probably because the difference is so small. I'll have to run a test myself once I have a little bit more time.
 
For me ODS was not showing the /.mobilebackups. Or the /.mobilebackups.trash originally.

However once I ran the terminal command from post 2. They showed up. Assuming once terminal read and sized them, ODS saw them and accounted for them.

And we aren't talking about small insignifcant sizes either /.mobilebackups.trash had ~111 GB and /.mobilebackups had another ~40 GB.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back