8bitclassics.com seems to have some.

Or if you are feeling adventurous: https://retrocomputing.stackexchange.com/questions/13319/how-can-i-make-an-external-psu-for-an-apple-iic

See what’s using the space. This will list any dirs using >100MiB:

sudo du -h -d 5 -t 100M /var

Did I read right that it doesn’t use systemd?

Obligatory: Debian.

But I’d be tempted to put Proxmox on it and then run containers for each function. Then you get purpose-crafted solutions for each use case, but can easily plug new functions in or shut them down based on what you decide later.

So. Much.

Wasted

Space

Copy on write is the difference. As I understand it, a btrfs snapshot takes no space when it’s created (beyond the file system record). The filesystem is always writing changes to file chunks as a new copy of the chunk, which is then recorded as a replacement of the old chunk (which is still present on-disk). So a snapshot tracks all of these later changes, and the file system keeps the old file chunks preserved as long as you keep the snapshot. That’s why you can mount a btrfs snapshot. It just shows you the volume through the lens of all of these saved changes.

When you delete a snapshot you are then marking these preserved chunks as free space. So that is also quick.