I assume the last argument in that command is the ID of the volume given in Cloudstack.
I get this output: file format: raw virtual size: 5.0G (5368709120 bytes) disk size: unavailable cluster_size: 4194304 On Tue, Dec 2, 2014 at 9:31 AM, Andrija Panic <andrija.pa...@gmail.com> wrote: > Tom, could you use the qemu-img to check the size of the volume on CEPH ? > Something like: qemu-img info > rbd:cloudstack/987c8d15-2401-4809-b721-280e496e57e4 > > On 2 December 2014 at 15:53, Tom Baine <thba...@gmail.com> wrote: > >> Hello, >> >> I've been trying to make use of the root disk resize feature >> implemented in 4.4 that allows instances to be deployed with a >> different sized root disk than the template it is deployed from. It >> looks like Cloudstack recognizes the rootdisk should be 100gb, but >> inside the instance the disk is reported as 5gb, the size of my >> template. >> >> My hypervisors are running Ubuntu 14.04 and are using Ceph/RBD for >> primary storage. I'm using cloudmonkey to deploy the VM with the >> following command attempts: >> >> deploy virtualmachine >> serviceofferingid=cebcf88c-22c7-4e62-9205-b929b898d532 >> templateid=709cecb1-0813-4e97-b2cc-8c2c2b3e7f4a >> zoneid=598dc4ea-3a01-493e-91b4-ba036d3342a8 rootdisksize=100 >> name=ubuntuCache domainid=29f1f9ee-39e6-11e4-ba61-00238be040f4 >> account=admin networkids=b9302918-9df0-4d9a-b384-32503f65ec7d >> hypervisor=kvm >> >> deploy virtualmachine >> serviceofferingid=cebcf88c-22c7-4e62-9205-b929b898d532 >> templateid=709cecb1-0813-4e97-b2cc-8c2c2b3e7f4a >> zoneid=598dc4ea-3a01-493e-91b4-ba036d3342a8 >> details[0].rootdisksize=100 name=ubuntuCache2 >> domainid=29f1f9ee-39e6-11e4-ba61-00238be040f4 account=admin >> networkids=b9302918-9df0-4d9a-b384-32503f65ec7d hypervisor=kvm >> >> Under the ACS UI > Instances > ubuntuCache > View Volumes > ROOTDISK, >> Size is listed as 100Gb. Inside the instance fdisk, gparted and >> hdparm -g on /dev/vda all show a 5gb disk size. I've tried forcing >> rescans of the SATA bus and the drive itself but didn't have any luck >> with that. Rebooting the instance also hasn't changed the reported >> size. >> >> Any thoughts would be appreciated, thanks. >> > > > > -- > > Andrija Panić
