{"id":53035,"date":"2026-08-28T14:47:29","date_gmt":"2026-08-28T18:47:29","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=53035"},"modified":"2026-09-09T10:56:54","modified_gmt":"2026-09-09T14:56:54","slug":"arent-snapshots-purgeable","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2026\/08\/28\/arent-snapshots-purgeable\/","title":{"rendered":"Aren’t Snapshots Purgeable?"},"content":{"rendered":"

Howard Oakley<\/a>:<\/p>\n

\n

Since High Sierra and APFS snapshots, accounting for purgeable space has been inconsistent and often misleading. I first reported this<\/a> over eight years ago in Sierra 10.12.6 and High Sierra 10.13.3, and most recently three years ago<\/a> in Ventura 13.3.1. This article looks at how this is handled now in Tahoe 26.6.2.<\/p>\n

[…]<\/p>\n

There is disappointingly little documentation on space management in macOS, and the closest Apple comes to defining purgeable space is in Disk Utility’s Help pages<\/a>, where it’s stated to be “space that macOS can free up when needed by removing files from your computer (you can’t manually remove the files that are designated purgeable, but macOS removes them as space is required)”.<\/p>\n

On the face of it, that includes cache files but not snapshots, as they can be manually removed in Disk Utility, as I’ve discussed in detail here<\/a>. This is contradicted when using tmutil localsnapshot<\/code> to make Time Machine snapshots, which reports that “local snapshots are considered purgeable and may be removed at any time by deleted(8)”, as deleted<\/code> is the purgeable space and cache management service in macOS.<\/p>\n

APFS snapshots can also be created by third-party apps that have the appropriate restricted entitlement. Apple doesn’t explain whether those too can be purged by macOS when additional free space is required.<\/p>\n<\/blockquote>\n\n

Howard Oakley<\/a>:<\/p>\n

\n

Before macOS will start copying a file to a volume, it checks whether there’s sufficient free space available. I believe this is normally performed by the FileCoordinator API<\/a> in Foundation, and appears in the log with the subsystem com.apple.foundation.filecoordination.<\/p>\n

If there isn’t sufficient free space to accommodate the file to be copied, deleted<\/code> in the subsystem com.apple.cache_delete checks whether enough space can be freed by purging items known to be purgeable in the destination volume. deleted<\/code> has a fixed set of services that can be called on to purge items, listed in \/System\/Library\/CacheDelete.<\/p>\n

[…]<\/p>\n

Space-based purging of Time Machine local snapshots is unreliable. The reason for this is that Time Machine CacheDelete fails to report purgeable space when it’s available. Even when it does work, it can take nearly half an hour for Time Machine CacheDelete to recognise the appearance of purgeable space.<\/p>\n<\/blockquote>\n\n

Sometimes you need to do it yourself with Disk Utility.<\/p>\n\n

Previously:<\/p>\n