You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rajesh Battala (JIRA)" <ji...@apache.org> on 2013/07/27 16:47:48 UTC
[jira] [Commented] (CLOUDSTACK-3878) After resizing the volume and
even after the operation is successful the volume size is not change in the
volume properties shown in UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721638#comment-13721638 ]
Rajesh Battala commented on CLOUDSTACK-3878:
--------------------------------------------
Attaching the UI screenshot
> After resizing the volume and even after the operation is successful the volume size is not change in the volume properties shown in UI
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3878
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3878
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API, Storage Controller, UI
> Affects Versions: 4.2.0
> Environment: KVM,
> 4.2 latest Head.
> cluster scope storage pool
> Reporter: Rajesh Battala
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: resizevolumebug.png
>
>
> 1. created an instance on KVM with default centos.
> 2. create vol of 5gb and attached the disk to the instance
> 3. resized the volume to 6 gb.
> on kvm the volume got resize successfuly.
> Sat Jul 27 20:09:40 IST 2013 - disk isn't the size we think it is: cloudstack said 0, disk said 5368709120.
> Sat Jul 27 20:09:40 IST 2013 - performed successful resize - currentsize:0 newsize:6442450944 path:/mnt/d26e1cfc-f04a-3eb5-8188-c18b4ebf2d6b/9cfcb5e5-6ed2-4b2b-8e92-29fd55a2bf38 type:QCOW2 vmname:i-2-23-VM live:true shrink:false
> but in UI, the volume size still is shown as 5GB only.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira