You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/03 14:58:10 UTC
[jira] [Commented] (CLOUDSTACK-9101) some issues in resize volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037800#comment-15037800 ]
ASF GitHub Bot commented on CLOUDSTACK-9101:
--------------------------------------------
GitHub user ustcweizhou opened a pull request:
https://github.com/apache/cloudstack/pull/1160
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
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ustcweizhou/cloudstack resize-volume-issues
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1160.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1160
----
commit 9077c9a5b47224b2d00978ff67e9af6957ec589b
Author: Wei Zhou <w....@tech.leaseweb.com>
Date: 2015-11-03T16:04:55Z
CLOUDSTACK-9022: keep Destroyed volumes for sometime
commit 4ed1e0d5f809d1bb2845b6e076d55eeb1ce3f0f4
Author: Wei Zhou <w....@tech.leaseweb.com>
Date: 2015-11-04T08:27:32Z
CLOUDSTACK-9022: move storage.cleanup related global configurations to StorageManager
commit 5b7d935ab0b35bec936785e44023ac0d8552e72b
Author: Remi Bergsma <gi...@remi.nl>
Date: 2015-12-02T20:52:46Z
Merge pull request #1145 from ustcweizhou/storage-cleanup-delay-4.6
[4.6.1] CLOUDSTACK-9022: keep Destroyed volumes for sometimefor now, the Destroyed volumes will be expunged in Storage cleanup thread, no matter when they are destroyed.
In Expunging vm thread, we expunge the Destroyed vms which have been destroyed at least 'expunge.delay' seconds. We add the similar configuration for volumes.
same to #1029 , for 4.6
* pr/1145:
CLOUDSTACK-9022: move storage.cleanup related global configurations to StorageManager
CLOUDSTACK-9022: keep Destroyed volumes for sometime
This closes #1029
Signed-off-by: Remi Bergsma <gi...@remi.nl>
commit 119b27b2c6c366949b574fbca1574f15d67a3af3
Author: Wei Zhou <w....@tech.leaseweb.com>
Date: 2015-12-03T10:54:20Z
CLOUDSTACK-9101: update volume size after resizevolume
commit d6e21f74163212b198731ddf23dd48bc4c787b84
Author: Wei Zhou <w....@tech.leaseweb.com>
Date: 2015-12-03T10:53:42Z
CLOUDSTACK-9101: add UI support for root volume resize
commit 9221cb3e0d0e5a0ea374f10e889f7e32c2a3eda1
Author: Wei Zhou <w....@tech.leaseweb.com>
Date: 2015-12-03T13:31:55Z
CLOUDSTACK-9101: resize root volume of stopped vm on KVM
----
> 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)