illumos gate

beadm's "Space" field appears to charge space in a straight forward but misleading manner (I'm guessing based on its behaviour for me)

- A BE is charged with the space consumed by itself and all descendent datasets.

This is misleading, because clone promotion means that the currently active BE is charged with the snapshot backing every other BE. So, my currently active BE is "34GB", but most others are around "200M".

It seems like it'd be more natural to charge a BE for the space used by its dataset and its origin snapshot.

That is something like this hacky script:

#!/bin/ksh

DSET=$1

function prop {
    zfs get -Hpo value $1 $2
}

origin=$(prop origin $1)

if [[ $origin == "-" ]]; then
    prop usedbydataset $DSET
else
    expr $(prop usedbydataset $DSET) + $(prop used $origin)
fi

Which charges my currently active BE with 6G and a random inactive BE with 1G, and seems generally more accurate calculation for how much disk space a given BE is actually causing to be consumed. That is, the amount of space which destroying the BE would free. ... that is, assuming I have my logic regarding ZFS space accounting correct.