3 ms·
btrfs used to have this issue, the problem being that the filesystem has to append metadata to do any operation including (ironically) deletion: https://serverf
by armchairhacker 3y ago
btrfs used to have this issue, the problem being that the filesystem has to append metadata to do any operation including (ironically) deletion: https://serverfault.com/a/478742 https://serverfault.com/a/478742.
AFAIK it's fixed now, because btrfs reserves some space and reports "disk full" before it's reached. macOS probably does the same (I'd hope), but it seems in this case the boundary wasn't enforced properly and the background snapshot caused it to write beyond.
- userbinator 3y agoIt looks like ZFS also suffers(ed?) the same problem: https://zfs-discuss.opensolaris.narkive.com/BQ7RMcjo/cannot-delete-file-when-fs-100-full https://zfs-discuss.opensolaris.narkive.com/BQ7RMcjo/cannot-...
- jclulow 3y agoYes, ZFS has the same fundamental issue that all COW file systems have here. We have a reserved pool of space that you can't use except for operations like removing stuff. The new problem with that reserved pool mechanism is that in 2024 it's probably way too big, because it's essentially a small but fixed percentage of the storage size. Don't let people use thresholds of total size without some kind of absolute cap!