Repository navigation
LINSTOR thin volumes become full-size volumes after reverting from a snapshot. #11765
Description
problem
As was discussed in #9950 After reverting volume from snapshot it allways became a full size volume instead of thin. Provisioning not changing, it's stays thin.
After fixes in the discussion, issue with creating new disks from snapshots has been resolved. New disks are created as thin volumes. However, the problem with disks during reverting from snapshots remains—they become thick volumes.
I am using version 4.19.3. I haven’t tried it, but I think this is also relevant for version 4.20.
versions
Ubuntu 24.04
ACS 4.19.3
Linstor 1.32.1
LVM-THIN
The steps to reproduce the bug
- Create volume snapshot
- Revert volume to snapshot state
- Volume became full-size
What to do about it?
After restoring disk from snapshot, disk must remains thin and not full-sized.
Activity
SviridoffA commentedon Sep 30, 2025
cc @rp-
rp- commentedon Oct 2, 2025
Can you get the log of the qemu command on the agent that is "restoring" the snapshot?
I think it can be seen with DEBUG logging
SviridoffA commentedon Oct 2, 2025
@rp-
Thank you for your reply. If I understand you correctly, you are referring to this command:
But just in case, I am attaching the full log output from the agent concerning two different virtual machines where the reverting is being performed. The disks of both virtual machines occupy 4.2 GB before reverting and 20 GB after. I am checking the disk sizes via linstor v l
1.txt
2.txt
rp- commentedon Oct 3, 2025
Yeah this looks like it doesn't use the sparse/discard options for converting the image.
I'll check if this wrong in the driver part or somewhere within CloudStack itself
rp- commentedon Oct 3, 2025
I found and fixed the issue if you are brave, you can give it a try with this .jar:
cloud-plugin-storage-volume-linstor-4.19.3.0.jar.gz
SviridoffA commentedon Oct 6, 2025
@rp- Thank you so much for this fix! I think I'll wait for the release, but just in case I change my mind, how do I upgrade plugin? Do I need to extract it to the /usr/share/cloudstack-management/lib folder, replacing what's there, and then restart the management server? Is this correct procedure?
Hi @DaanHoogland Is there a chance this fix will be included in version 4.20.2?🙏
rp- commentedon Oct 6, 2025
This fix is actually for the agent side, so you would need to replace it in
/usr/share/cloudstack-agent/lib, but this .jar has also additional fixes, not yet in 4.19.3.0, which also use management server code.DaanHoogland commentedon Oct 7, 2025
We must merge the 4.19 branch forward to get it in (we usually don’t forget 😉 )
DaanHoogland commentedon Oct 31, 2025
fixed in #11787