11/25/2023 0 Comments Disk utility free space![]() ![]() Restore Time Machine settings by adding the two volumes back to the exclusion list before remounting Time Machine backup storage.Drag the large files in TestVolume1 to the Trash and empty it, leaving both volumes empty.Using Disk Utility, confirm that a snapshot has been made of TestVolume1.Note that snapshots made by third-party tools may not behave the same as those of Time Machine, and may not be included in Purgeable space. Open Terminal and enter the command tmutil localsnapshot, which will then make snapshots of all volumes being backed up, including both TestVolume1 and TestVolume2.Open Time Machine settings and remove TestVolume1 and TestVolume2 from the list of excluded volumes, enabling Time Machine backups for those two volumes.Unmount all current Time Machine backup storage, to ensure test files aren’t backed up to it.This requires making a snapshot of at least TestVolume1, then deleting the files making up the 94 GB of Used space. The next step is to turn the current Used space on TestVolume1 into Purgeable space, which is a little more complicated. ![]() TestVolume2 has a Capacity of 100 GB, 6 GB Available, and Other Volumes have 94 GB Used. TestVolume1 has a Capacity of 100 GB, 6 GB Available, 94 GB Used, and none Purgeable, which is also correct. The container has a Capacity of 100 GB, with 94 GB Used and 6 GB Free, which is correct. Here, I used my free app Stibium to write two files each of 47 GB for a total of 94 GB. Then write large files to TestVolume1 to almost fill the container. In this case, I have named those two volumes TestVolume1 and TestVolume2. ![]() Although you can do this using a single partition including the whole of the disk, it’s simplest to repartition the disk with a relatively small APFS container, such as 100 GB, using Disk Utility.Īdd a second volume to your test container, also in plain APFS format. This is best performed on an external disk formatted in APFS, containing no other data. This demonstration provides a reproducible sequence to demonstrate them, and the confusion this causes in users. There are innumerable reports of that available space not being realised in practice, and of huge errors in reporting purgeable and available space. Hence, when declaring space available in a volume, macOS will usually give that currently free plus that designated purgeable. ![]() Should a file operation, such as copying a file to a volume, require more space than is currently free, then macOS is claimed to delete items deemed purgeable to augment free space and enable the operation to complete. Although Apple provides a conceptual guide to programming the file system, it hasn’t been updated for over four years and doesn’t cover macOS space management at all.Īt its heart is the equation (whose origin is obscure)Ĭapacity = Available + (Used – Purgeable) This space management is based on the concept of purgeable files, as mentioned in Disk Utility’s Help pages and discussed in detail here. This article demonstrates these in an edge case for clarity. Furthermore, information given to users is inconsistent across the Finder and Disk Utility, and appears riddled with bugs that only confound the user. These aren’t explained in any coherent way in user documentation, nor can I find any explanation provided to developers. Started APFS operation Aligning grow delta to 45,685,575,680 bytes and targeting a new physical store size of 250,685,575,168 bytes Determined the maximum size for the targeted physical store of this APFS Container to be 250,684,547,072 bytes Resizing APFS Container designated by APFS Container Reference disk1 The specific APFS Physical Store being resized is disk0s2 Verifying storage system Using live mode Performing fsck_apfs -n -x -l /dev/disk0s2 Checking the container superblock Checking the EFI jumpstart record Checking the space manager Checking the space manager free queue trees Checking the object map Checking the encryption key structures Checking volume /dev/rdisk1s1 Checking the APFS volume superblock Checking the object map Checking the snapshot metadata tree Checking the snapshot metadata Checking the extent ref tree Checking the document ID tree Checking the fsroot tree error: extended attribute (id 49614545): invalid dstream.MacOS superimposes additional space management features over APFS to make some file system contents purgeable when it runs short of free space. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |