You should never use LVM tools directly with LXD volumes, as LXD will not know about the operation and its state will get out of sync, potentially causing issues.
Why did you change from lxc config device set (as in the first command) to lxc config device override (in the second command)? The first command using set would have allowed you to change the size to 200GB.
Yes, I have 1st generate “lxc config set” command and reboot my container. after reboot I have checked the size it is ok. Then I am again trying to increase my container disk by “lxc config device override” for testing purposes but it doesn’t work. What is the procedure to again increase container lvm disk?
If it is a new container (using the profile’s disk), then use override, that will copy the root disk config from the profile into the container and override the size property.
lxc config device override con3 root size 200GB
Then on subsequent modifications use the set command:
When providing the -s flag to lxc init or lxc launch, it will override the root device at create time to modify it’s storage pool. So you just need to use lxc config device set con4 root size after that.