Closed ykazakov closed 2 years ago
"lxd init" cluster questions can be a bit confusing as they're generated based on the existing config and so doesn't really allow for a curated flow like the one you get on standalone systems.
In this case the size property is asked because you could have answered the source property with an empty string, causing LXD to create a loop file for your pool which does use the size property.
However whenever passing in an existing block device or VG, that property is meaningless.
I see. Could it, perhaps, make sense to allow some sensible default value, e.g., 0 = Autodetect? I do not think many would create a cluster with a loop file.
Well, except for all of the ones that are built in VMs for testing where they'll usually default to ZFS on loop and so will use the property :)
There effectively are defaults for most if not all of those, you can leave them empty, they just may not be defaults that you like! In this case leaving both of them empty would have resulted in a loop backed LVM pool with the size using LXD's default size (percentage of available space with a fixed minimum/maximum allocation).
Required information
Issue description
Upon joining an existing cluster lxd asks for the size of the local storage pool. However this value does not seem to be used.
Steps to reproduce
Strangely, the total and used space still does not match the size of the file system: