canonical
Ceph-based pool info should display overall projected utilization of the pool
$ lxc storage info ceph1 info: description: "" driver: ceph name: ceph1 space used: 12.00KiB total space: 9.23GiB
$ lxc storage volume info ceph1 t1 Name: t1 Type: custom Content type: block Usage: 0B Total: 4.00GiB
Ceph allows thin provisioning hence real utilization of the pool is low when the volume is created empty. However this may lead to quick over provisioning of the storage from LXD because the pool doesn't count the logical maximum of the volume size. Ideally the "Used" field should display the overall capacity of the volumes in the pool rather than current real utilization of the backend, to avoid over provisioning.
Ideally the "Used" field should display the overall capacity of the volumes in the pool rather than current real utilization of the backend, to avoid over provisioning.
This will potentially be different depending on different people's perspective.
We also need to consider how this compares to the meaning of that field for other storage pool drivers (such as ZFS, BTRFS, LVM etc) that also have the concept of thin provisioning.
Its also worth considering and reviewing how sparse files in dir and btrfs pools are counted towards this figure.
So I don't think this is something we can change lightly, and perhaps we need to introduce another field that represents "allocated" space rather than actual used space.
