News for hackers. Stuff that matters.

A comment on A disk so full, it couldn't be restored. Parent comment

Re:A disk so full, it couldn't be restored by rincebrain on Thursday April 04, 2024 @04:07AM (#39927723)
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.

[ Parent | on HN ]
Re:A disk so full, it couldn't be restored by p_l on Thursday April 04, 2024 @04:23AM (#39927801)
Yeah, a situation where you pool gets suspended due to no space and you can't delete files is considered a bug by OpenZFS.
[ Parent | on HN ]
Re:A disk so full, it couldn't be restored by rincebrain on Thursday April 04, 2024 @11:53AM (#39931992)
I mean, the pool should never have gotten suspended by that, even before OpenZFS was forked; just ENOSPC on rm.
[ Parent | on HN ]
Re:A disk so full, it couldn't be restored by aidenn0 on Thursday April 04, 2024 @09:24AM (#39930098)
Oh, that's good to know. I hit it in the past, but it was long enough ago that ZFS still had format versions.
[ Parent | on HN ]
Re:A disk so full, it couldn't be restored by rincebrain on Thursday April 04, 2024 @11:51AM (#39931966)
Yeah, the whole dance around slop space, if I remember my archaeology, went in shortly after the fork.
[ Parent | on HN ]
Re:A disk so full, it couldn't be restored by MarkSweep on Thursday April 04, 2024 @12:29PM (#39932607)
For more details about this slop space, see this comment:

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

[ Parent | on HN ]