3 ms·
Still, you should not be able to brick your device into a state like this with legitimate, normal, non elevated operations. If the POSIX API does have some lim
by sspiff 3y ago
Still, you should not be able to brick your device into a state like this with legitimate, normal, non elevated operations.
If the POSIX API does have some limitation which would prevent this error from occurring with higher level APIs (which I sincerely doubt), macOS should simply start failing with errno = ENOSPC earlier for POSIX operations.
There is no other system that behaves like this, and we wouldn't be making excuses like this if Microsoft messed something basic up like this.
- willyt 3y agoI agree, though others are saying that BTRFS and ZFS can also get into this state.
- sspiff 3y agoI'd have to try, but have never encountered something like it on btrfs (though to be fair I've had many other issues and bugs with it over the years!) I understand the logic, but typically I've seen filesystem implementations block writes once metadata volumes become close enough to full. Also, and I don't know if this is a thing on modern filesystems, you used to be able to reserve free space for root user only, precisely for recovering from issues like this in the past.