{"id":28815,"date":"2020-04-28T17:04:14","date_gmt":"2020-04-28T21:04:14","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=28815"},"modified":"2020-04-28T17:04:14","modified_gmt":"2020-04-28T21:04:14","slug":"apfs-sparse-bundle-bugs","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/04\/28\/apfs-sparse-bundle-bugs\/","title":{"rendered":"APFS Sparse Bundle Bugs"},"content":{"rendered":"

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

\n

One of the strangest and most irritating bugs with sparse bundles in APFS format is the unreliability of their estimates of size and free space. Whether you look at free space shown in the Finder or in Disk Utility, there is no correlation between what is shown and what is actually available for use in the sparse bundle.\n\nFor example, the smallest APFS sparse bundle allowed is 8.4 MB, which is stated as having 8 MB of free space. Yet you’ll find it impossible to copy a 7 MB file to that sparse bundle, as you’ll be told that it’s full even when it’s completely empty. macOS simply refuses to let you use the claimed free space on APFS sparse bundles, although HFS+ sparse bundles aren’t as unreliable.<\/p>\n

[…]<\/p>\n

Despite their widespread use and advantages, macOS features supporting the use of APFS-format sparse bundles are at present riddled with bugs (I count 6 above) and have serious shortcomings. Their inability to self-compact is a major failing which makes their use clumsy at best, and Disk Utility’s lack of support for basic maintenance functions through the last 2.5 years reflects badly on Apple’s engineering priorities. Disk Utility remains of early beta-test quality and far from complete.<\/p>\n<\/blockquote>\n\n

I don’t see much reason to use APFS disk images, except for testing how an app works with APFS. HFS+ sparse bundles are dependable and can be compacted<\/a> with DropDMG<\/a>.<\/p>\n\n

The Disk Utility reliability problems go back to the rewrite in macOS 10.11. Usually the command-line tools work better.<\/p>\n\n

Previously:<\/p>\n