Turns out I can truncate it to any size I wanted to, regardless of disk space. While it would be interesting to hear why that is possible, I am more interested in making it consistent between the profile settings and zfs. This is not consistent (1.05TB + 775G is not 1800GB)
I’d like to make the two match at 1.8TB, and leave the rest for the host system.
volume.size refers to the size of volumes that will be created on your pool, this should definitely not be set to the entire pool or it would make it quite easy for a single instance to use all the space
You should probably just lxc storage unset default volume.size and let LXD handle the default in your case.
The size property can also be completely ignored. It’s effectively set to the size which was originally requested by the user at the time the pool was created but is otherwise currently completely ignored by LXD.
Out of the box there are no quotas set on the filesystem datasets as used for containers and custom storage volumes.
The only thing that’s fixed size in ZFS are volumes and those are only used for block based custom volumes and for VMs. Those default to 10GiB, they can be grown later by manually overriding their size, they however cannot be shrunk.