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

System Data HUGE - 700GB. Help!

lwilliams said:
More specifically, neither me nor Apple can find the data......and, therefore, cannot delete it. Even going into all the "hidden" folders, nothing anywhere adds up to 661GB of data.

So, no. There is no error because it can't be found.

The TimeMachine snapshots that are showing add up to a little over 13 TB. So, those can't be sitting on the 1 TB SSD.
Click to expand...
With all due respect, did you read the thread?

APFS snapshots aren’t files. They’re effectively lists of file diffs (along with metadata like file size). The snapshots themselves are small, but Time Machine keeps these local snapshots/lists and keeps the underlying files around in APFS, even if they appear to have been deleted, in case you need them when your backup location is unavailable. This is why you can appear to have many terabytes’ worth of snapshots on a 1 TB SSD. As Apple’s documentation and comments here have noted, these snapshots are local to your device and completely unrelated to your Time Machine backups stored elsewhere.

APFS snapshots do not show up as regular files, which is exactly why you can’t see any data adding up to 600+ GB in the Finder.

Especially during times of great file churn (like a bunch of big app updates), snapshots will grow in size because the diffs get larger. The system is supposed to automatically purge APFS snapshots when they’re over 24 hours old or disk space is needed. This doesn’t always happen in practice, in which case you must delete the snapshots manually (instructions for which are earlier in the thread).

I agree that you shouldn’t have to wipe the machine, which is why I and others have suggested that you try deleting the APFS snapshots first.
 
  • Like
Reactions: Ben J.
lwilliams said:
I have backups to TimeMachine on a NAS (QNAP).

BTW - I am a certified IT Pro (A+, CCNA, Security+, MCSE, Cloud+, CISSP and PMP) - 31 years as an IT Director.
Click to expand...

With respect, these two statements are incongruous to me. But hey, looks like you've got this well in hand, champ.
 
Last edited:
  • Like
Reactions: ConvertedToMac
Have you tried running Onyx? Run Maintenance with the preselected options. I use iCloud and toggled off Optimize Storage since I have a 2TB SSD and I didnt want to give iCloud the option of only keeping files in the cloud even though it says it will only do that if I am low on space. Anyhow just switching that off my System Data jumped from 22GB to 280GB (MBP M5). So then I switched back to Optimize Storage, rebooted, and it was still 280GB. So I ran Daisy Disk and it didn’t show anything in the 280GB range and System Data according to Daisy Disk was still around 28GB. I ran the default Onyx Maintenance routines which then reboots the system, and when I checked again the System Data was back down around 22GB.

I think in general I don’t 100% trust the values macOS gives me in the Storage settings. They sometimes differ from what I see in Disk Utility and tools like iStat Menu and Daisy Disk.

Anyhow, if Apple can’t figure it out after 3+ hours dinking around, time to nuke your system from orbit. It’s the only way to be sure. 😉
 
jonblatho commented:
"I agree that you shouldn’t have to wipe the machine, which is why I and others have suggested that you try deleting the APFS snapshots first."

Your point is well taken.
OP should try your suggestion first.
BUT...

If that doesn't seem to work for him, I suggested (in reply 22) that he use the "erase all content and settings" option BECAUSE it works quickly and smoothly.

BUT HE MUST HAVE A GOOD BACKUP.

I don't know how much personal data is on the OP's internal drive, but if it's not too much, the erase/restore shouldn't take very long at all.
The "erase all content" and "restoration" to "moment zero" goes very quickly. I report this from my own "test experience" using a 2021 MacBook Pro (m1pro).

Then, the migration from my backup drive (during the once-again-initial-setup) went fast as well (because I don't keep a lot of stuff on the MBP).

If the OP has many GB's of stuff from his backup, well... then it will take a little longer.

I suggested creating/using a cloned backup because I believe those actually migrate faster than a tm backup...

Finally, the reason to use the "erase all content and settings" is because -- like conmee quips about in the reply above this one -- "nuking it from orbit is the only way to be sure" ...
 
I just came across the same problem.

Worth checking - do you use Adobe CC?

Their cache files take up a lot of storage.
Macintosh HD > Users > You > Library > Caches > Adobe

When some apps update, they don't delete caches from their previous versions. I found an old version hogging 60GB, and my most recent version had just eaten 270GB. Delete these, and setup limits inside each Adobe app. But be wary that if it updates, this may happen again.
 
No Adobe here.

I found that it was uncomplete Time Machine backups. They stay there forever. They are not supposee to do that, according to conversation with Apple.

I just started using Disk Utility about twice a month and delete any that are lingering there. Solved the problem for me. Though, it is a problem that should not exist.

.
 
lwilliams said:
No Adobe here.

I found that it was uncomplete Time Machine backups. They stay there forever. They are not supposee to do that, according to conversation with Apple.

I just started using Disk Utility about twice a month and delete any that are lingering there. Solved the problem for me. Though, it is a problem that should not exist.

.
Click to expand...
I agree; that's really weird. A failed backup isn't a backup, so into the trash it goes. At least you figured it out.
 
lwilliams said:
No Adobe here.

I found that it was uncomplete Time Machine backups. They stay there forever. They are not supposee to do that, according to conversation with Apple.

I just started using Disk Utility about twice a month and delete any that are lingering there. Solved the problem for me. Though, it is a problem that should not exist.

.
Click to expand...
Since you can delete them in Disk Utility it sounds like you are referring to Time Machine Local (ie boot volume) snapshots They are not incomplete back ups, but they are supposed to be deleted after 24hrs so you should never have more than 24 or 25.

They are incredibly useful for rolling back the whole machine really quickly, which I have done after a misstep when it was clear rolling back was going to be much easier than repairing the issue. They are also useful if you have your tM backup drive disconnected for up to a day, as the snapshots include the hourly backups that would have been made to the backup drive.

Rolling back with TM local snapshot seems to be little known and not documented by Apple. Howard Oakley of Eclectic Light had an article about it recently.
 
OP wrote:
"I found that it was uncomplete Time Machine backups. They stay there forever. They are not supposee to do that, according to conversation with Apple."

Solution:
- Stop using time machine
- START using either CarbonCopyCloner or SuperDuper.

With CCC, you can choose to either maintain snapshots, or not use them at all (I choose the latter -- I don't want anything to do with "snapshots").

Both CCC and SD are free to download and use for 30 days or so.
I suggest you give them BOTH a try...
 
Time Machine is great, any hater doesn't know how to use it properly. It's supposed to fill up your drive and it automatically deletes all your old backups on its own.

For example, my OS drive is 4TB, I got a 8TB HDD for Time Machine, plenty of space to have backups that go back months.

For anything serious, use a NAS/external drives and do an offsite backup.
 
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