[
https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930448#comment-13930448
]
Marcus Sorensen commented on CLOUDSTACK-6181:
---------------------------------------------
Ok. I believe this is a separate issue that was introduced by another change,
and likely affects the existing data disk resize as well. I'm curious, you
mention that you see this with offline volume (meaning that the vm is stopped,
correct?), does that work with running VMs?
It looks like perhaps it's related to passing the flag
VIR_STORAGE_VOL_RESIZE_ALLOCATE, which seems to be to make the new resized size
not sparse by using posix_fallocate. I'm looking through to see when it was
implemented, and I found someone from redhat adding it for raw images. It kind
of seems as though it's
The same thing could supposedly be tested with virsh like so : "virsh
vol-resize /var/lib/libvirt/images/sparse.raw 6M --allocate" It would be
interesting to know if it works for a raw img file but not qcow2, and your
libvirt version.
> Root resize
> -----------
>
> Key: CLOUDSTACK-6181
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Storage Controller, UI
> Affects Versions: 4.4.0
> Environment: KVM/libvirt/CentOS, Xenserver
> Reporter: Nux
> Labels: disk, resize, template
> Fix For: 4.4.0
>
>
> Rationale:
> Currently the root size of an instance is locked to that of the template.
> This creates unnecessary template duplicates, prevents the creation of a
> market place, wastes time and disk space and generally makes work more
> complicated.
> Real life example - a small VPS provider might want to offer the following
> sizes (in GB):
> 10,20,40,80,160,240,320,480,620
> That's 9 offerings.
> The template selection could look like this, including real disk space used:
> Windows 2008 ~10GB
> Windows 2008+Plesk ~15GB
> Windows 2008+MSSQL ~15GB
> Windows 2012 ~10GB
> Windows 2012+Plesk ~15GB
> Windows 2012+MSSQL ~15GB
> CentOS ~1GB
> CentOS+CPanel ~3GB
> CentOS+Virtualmin ~3GB
> CentOS+Zimbra ~3GB
> CentOS+Docker ~2GB
> Debian ~1GB
> Ubuntu LTS ~1GB
> In this case the total disk space used by templates will be 828 GB, that's
> almost 1 TB. If your storage is expensive and limited SSD this can get
> painful!
> If the root resize feature is enabled we can reduce this to under 100 GB.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
