![]() In CCC, you can have snapshots made by whatever schedule you like if you simply create a dummy task that clones an empty folder on your disk to another empty folder. So if snapshots effectively allow some history on the same drive even without an external backup, perhaps I'll change my thinking on APFS. If that’s progress, I hope progress slows.Ĭarbon Copy Cloner is terrific, but Time Machine helps me more for little stuff, like overwriting a blog post by accident ('git' can deal with that too, but using git is harder). MPG: from my perspective as a user, APFS is a solution in search of a problem, while bringing confusion and performance problems. It's confusing at first, but at least it's correct. ![]() indicated free space on the volume etc.).Īt the moment, I think the safest bet is to rely on CCC for anything critical, especially regarding backup. Disk Utility) to give hugely differing numbers free disk space, and even within the Finder basic arithmetic seems like a foreign concept (sizes of individual files vs. ![]() And it gets even more complicated because of "cloned" files and similar APFS features, which cause different apps (e. g. They basically hide from the user that there even are such things as snapshots, let alone how they work or how they impact free disk space. That way you can also find out how much space you can free by deleting multiple snapshots at once.Īll this does indeed seem counter-intuitive and unnecessarily complex, but I think it simply can't be done much differently due to the referential nature of snapshots.Īpple's apps are another matter, of course. You would also get the same number if you selected all individual snapshots on the right and right-clicked them (the number is calculated and then shown in the context menu). You can always see how much space is occupied by snapshots in total by looking below the bar on the left-in your case, 260.41 GB. The reason for this difference is that snapshots often include files also included in other snapshots those files only get deleted if every snapshot containing them gets deleted, so the number for "how much space do I get back if I delete this single snapshot" is often considerably lower. The key to understanding that window is that the sizes given for individual snapshots represent how much space would be freed (immediately) if you deleted that snapshot, NOT how much space the files referenced in the snapshot occupy. I was having the same basic issue with snapshots and CCC. What is 260GB “purgeable” and how can I get rid of it? And why does the Finder show 1.36GB purgeable? Reader Sebastian B writes: It’s ludicrous to have to manually calculate space when the Finder ought to do it-I want “used” to tell me how much space I’ll need to back stuff up. I assume it is some kind of snapshot, but whether it has any utility remains to be seen. Iterating over the actual files, the total size matches T5_MasterClone, from which it was cloned. Below, the APFS volume later grew to have 260GB of “purgeable”-but there is no way to purge it that I can find (I don’t use iCloud for storage, so it’s not involved). The purgeable space concept on APFS is mystifying. Purgeable space and snapshots, Time Machine and Carbon Copy Cloner The list above is just the initial problems. While I cannot blame Apple for the 1Password thing, the rest of it is a lousy experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |