Hacker News new | past | comments | ask | show | jobs | submit login

This hasn't been a problem you should be able to hit in ZFS in a long time.

It reserves a percent of your pool's total space precisely to avoid having 0 actual free space and only allows using space from that amount if the operation is a net gain on free space.




For more details about this slop space, see this comment:

https://github.com/openzfs/zfs/blob/99741bde59d1d1df0963009b...


Yeah, a situation where you pool gets suspended due to no space and you can't delete files is considered a bug by OpenZFS.


I mean, the pool should never have gotten suspended by that, even before OpenZFS was forked; just ENOSPC on rm.


Oh, that's good to know. I hit it in the past, but it was long enough ago that ZFS still had format versions.


Yeah, the whole dance around slop space, if I remember my archaeology, went in shortly after the fork.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: