Here's another #techromancy tip:
Create a 2GB "sacrificial" file for your volumes. When the disk fills up and your system locks up, kill it and run your cleanup scripts. It's helped me get out of a bind a few times now.
```bash
dd if=/dev/urandom of=sacrifice.txt bs=1M count=2048
```
```bash
rm sacrifice.txt
```
Hit that bell icon for more techromancy tips and cyberlifehacks
@mauve wouldn't fallocate be a better command for that? with dd, you actually have to wait for the full amount to be written to the drive, which is not insignificant
@esoteric_programmer Generally I try to use "real data" to avoid edge cases where the empty space is being compressed with "sparse files" (or whatever it was called)
@esoteric_programmer probably better for like 99% of cases though, good idea!
@mauve
It might also be a good time to revise the "reserved blocks" on your file system (assuming you are using ext4): in principle, these should keep the system operational while your download fills the volume as they are kept as a last reserve for root and root-owned daemons. Typical value is 5% of the volume but the exact default percentage can vary.
If you are using a home-only partition or a large (>50GB) volume you could claim back some of that space: https://wiki.archlinux.org/title/Ext4#Reserved_blocks
@mauve OMG this is actually such a good idea