Resize LXD container

Right, if not using the snap, then you don’t have the potential metadata corruption issue.

You will still hit a potential issue if you ever do migration or rely on project usage quotas as both of those require the size property to be set and match up with what’s in LVM. In the case of migration, that’s used to properly size the volume on the target, so it not matching will cause the migration to fail. In the project case, project quotas are evaluated against size information in the database, if you manually grow stuff, it won’t be represented in the usage.

2 Likes