rohityadavcloud commented on issue #7934: URL: https://github.com/apache/cloudstack/issues/7934#issuecomment-1704365221
Thanks @sbrueseke @rp- , @rp- is right in case of LVM-thin, the allocated volume size seen in `linstor vd l` showed like 2.2GB (template size) instead of the root disk allocated size (100GB) in my case. Like I've mentioned briefly, I've workaround specifically by using `set-size` in `linstor vd` I could change the volume size to 100GB and do a VM stop/start. Resize didn't work for me though, I can try to test again. @rp- on the last point, I wanted to learn how the linstor plugin caches the template. In my experimentation, I found the issue to be a case where a Linstor (resource) volume fails to be deleted (stuck in Destory state but not expunged in CloudStack's DB), CloudStack can mark it as removed in its database but the volume may not be deleted on the linstor side. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
