cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9101) some issues in resize volume
Date Sun, 06 Dec 2015 18:45:11 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044026#comment-15044026
] 

ASF subversion and git services commented on CLOUDSTACK-9101:
-------------------------------------------------------------

Commit 998b1ba629bfdf3ea26fd515ad62f26260dee060 in cloudstack's branch refs/heads/4.6 from
[~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=998b1ba ]

Merge pull request #1161 from ustcweizhou/resize-volume-issues

CLOUDSTACK-9101: fix some issues in resize volume(1) fix issue: volume size is not updated
even if the operation succeed
(2) Add ui support for root volume resize
(3) resize on qcow2 type ROOT volume of stopped vm does not really work
see https://issues.apache.org/jira/browse/CLOUDSTACK-9101

* pr/1161:
  CLOUDSTACK-9101: resize root volume of stopped vm on KVM
  CLOUDSTACK-9101: add UI support for root volume resize
  CLOUDSTACK-9101: update volume size after resizevolume

Signed-off-by: Daan Hoogland <daan@onecht.net>


> some issues in resize volume
> ----------------------------
>
>                 Key: CLOUDSTACK-9101
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9101
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Wei Zhou
>            Assignee: Wei Zhou
>
> I found some issues in the testing of resizeVolume
> (1) it is not implemented on UI
> (2) volume size is not updated even if the operation succeed
> mysql> select volumes.id,volumes.size,disk_offering.disk_size from volumes left join
disk_offering on volumes.disk_offering_id=disk_offering.id where volumes.uuid='999b8ad2-3664-44b9-8cf6-985e60a98cc8';
> +------+-------------+-------------+
> | id   | size        | disk_size   |
> +------+-------------+-------------+
> |   45 | 85899345920 | 85899345920 |
> +------+-------------+-------------+
> | id   | size        | disk_size   |
> +------+-------------+-------------+
> | 7530 | 5368709120  | 21474836480 |
> +------+-------------+-------------+
> 1 row in set (0.00 sec)
> (3) on KVM, the resize on running vm is good
> root@KVM015:~# qemu-img info /mnt/f773b66d-fd8c-3576-aa37-e3f0e685b183/e9ddd9b1-57c4-4ad7-b950-7b7f5c5cf2dc
> image: /mnt/f773b66d-fd8c-3576-aa37-e3f0e685b183/e9ddd9b1-57c4-4ad7-b950-7b7f5c5cf2dc
> file format: qcow2
> virtual size: 41G (44023414784 bytes)
> but root volume on stopped vm is not correct
> root@KVM015:~# qemu-img info /mnt/1dcbc42c-99bc-3276-9d86-4ad81ef1ad8e/2412a4c0-8271-4e21-a3d1-61b041d209d6
> image: /mnt/1dcbc42c-99bc-3276-9d86-4ad81ef1ad8e/2412a4c0-8271-4e21-a3d1-61b041d209d6
> file format: qcow2
> virtual size: 40G (42949672960 bytes)
> (4) resource count of primary_storage is not updated after restorevm, if the root volume
has been resized before.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message