What I think would help any COW file system is delay snapshot (and clone) deletion longer, and delete in groups, which would result in larger contiguous regions being freed. When one container is deleted, a small amount of space is freed, and then may be used for writes, quickly filling up, and thus increasing localized fragmentation - or more problematically for spinning drives it&#x27;s increasing seek times by causing recent writes to be scattered farther apart. To reduce read and write seeks, it&#x27;s better to have larger free areas for COW to write to sequentially.<p>So it&#x27;d be nice if there were something like a &quot;remove&#x2F;hide&quot; feature for containers, separate from delete or clean up, with a command that makes it easier to select many containers for deletion. At least on Btrfs this should be quite fast, and the background cleaner process that does the actual work of updating the ref count and freeing extents should have a priority such that it doesn&#x27;t overly negatively impact other processes.<p>Some of this behavior may change on Btrfs as the free space tracking has been recently rewritten. Right now the default is the original space cache implementation, while the new free space b-tree implementation is a mount time option intended only for testing.