AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Macos show hidden files catalina9/12/2023 ![]() ![]() ![]() I tried deleting the snapshots by their "XID", but that didn't seem to work for all of them, so I instead deleted them by name: -bash-3.2# diskutil apfs deleteSnapshot disk2s1 -name com.ĭeleting APFS Snapshot XID 10440723 "com." from APFS Volume disk2s1 bash-3.2# diskutil apfs listSnapshots disk2s5 NOTE: This snapshot sets the minimal allowed size of APFS Container disk2 I listed their snapshots: -bash-3.2# diskutil apfs listSnapshots disk2s1 Then I mounted them: -bash-3.2# diskutil mount disk1s1 bash-3.2# diskutil apfs unlockVolume disk1s5 I think (I don't remember precisely) unlocked the volumes with: -bash-3.2# diskutil apfs unlockVolume disk1s1 Running diskutil list, I found that my data and system volumes were assigned the labels disk1s1 and disk2s5, respectively. However, this required first unlocking and mounting the relevant volumes. From there, I did a similar process to try to delete the snapshots. I loaded up into recovery mode, and went to the command line. This might have something to do with the read-onliness of the system volume, or to do with it being the actively booted volume, but I don't know. Strangely, even though I'm using sudo to run the command as root, I'm told I have insufficient privileges. Then I tried deleting them manually: $ sudo diskutil apfs deleteSnapshot disk1s1 -uuid BFD78F4F-99BB-4D5B-AE16-5367DC9C615Eĭeleting APFS Snapshot BFD78F4F-99BB-4D5B-AE16-5367DC9C615E "com." from APFS Volume disk1s1 NOTE: This snapshot limits the minimum size of APFS Container disk1 First, I listed the APFS snapshots to see their UUIDs: $ sudo diskutil apfs listSnapshots /System/Volumes/Data The response says they were deleted, but they actually weren't: $ tmutil listlocalsnapshotdatesĪt this point, I start going the nuclear route: directly using diskutil to delete the APFS snapshots, without Time Machine's blessing to do so. $ sudo tmutil deletelocalsnapshots -214224 I tried manually deleting these: $ sudo tmutil deletelocalsnapshots -233121 In my case, there were two snapshots remaining that persisted even after thinning: $ tmutil listlocalsnapshotdates the issue is that deleting any number of snapshots won't matter if even one snapshot exists holding onto the same data. Manual snapshot deletionĪfter some number of snapshots were deleted, some space was freed up, but not much. If the system could get this to work automatically, I don't see why manually invoking it would help. Listing some number of deleted snapshots. ![]() If this succeeded, it should say something like Thinned local snapshots: This requests Time Machine to automatically clean out enough snapshots to free a desired amount of space, in this case, 100 GB. Deleting a file of X bytes would increase the size of this "hidden space" by X bytes.įirstly, I would try to manually thin out the Time Machine snapshots.
0 Comments
Read More
Leave a Reply. |