Hi Stéphane,
As you have seen, it was difficult for me to recognize that a disk-image was being used. In the single instance mode it was easier using “lxc storage info NAME” and look at the “source” column.
I currently have containers on both nodes because I’m moving from my old Server the the new one.
Therefore, I first decided to expand the disk file:
# truncate -s + 200G /var/snap/lxd/common/lxd/disks/default.img
I did not manage to expand the BTRFS from “inside”:
# nsenter --mount = /run/snapd/ns/lxd.mnt ./snap/lxd/current/bin/btrfs filesystem resize max /var/snap/lxd/common/lxd/storage-pools/default Resize '/ var / snap / lxd / common / lxd / storage-pools / default' of 'max'
But the available size was still the old one.
Then I mounted the disk-image via the loop (Resize LXD BTRFS storage space - #9 by gpatel-fr) not nice but effective.
I now have enough space to complete the migration.
I then plan to dissolve the cluster and create a new pool without a disk-image.
After moving to the new pool, I can delete the disk-image.
This behavior is not optimal(!) and I suggest that the initialization be changed so that the user can choose how the pool is created.
Have you any Ideas or suggestions?
Thanks Frank