cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Sadhu <Suresh.Sa...@citrix.com>
Subject RE: custom size of disk offering.
Date Fri, 13 Mar 2015 16:09:04 GMT

You can manually  resize the root partition safely by extending lvm partition .
/dev/sda is your  root partition  right   and what is this /dev/vda?

Please refer blow link  :  I have used below link to resize my root partition .
http://www.rootusers.com/how-to-increase-the-size-of-a-linux-lvm-by-adding-a-new-disk/


-----Original Message-----
From: Dan Dong [mailto:dongdan39@gmail.com] 
Sent: 13 March 2015 21:25
To: users@cloudstack.apache.org
Subject: Re: custom size of disk offering.

Hi, Andrija,
  Here is the result:
ubuntu@node100GB:~$ sudo fdisk -l

Disk /dev/vda: 107.4 GB, 107374182400 bytes
16 heads, 63 sectors/track, 208050 cylinders, total 209715200 sectors Units = sectors of 1
* 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal):
512 bytes / 512 bytes Disk identifier: 0x00000000

Disk /dev/vda doesn't contain a valid partition table

Disk /dev/sda: 10.7 GB, 10737418240 bytes
4 heads, 32 sectors/track, 163840 cylinders, total 20971520 sectors Units = sectors of 1 *
512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal):
512 bytes / 512 bytes Disk identifier: 0x000b2a28

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    20971519    10484736   83  Linux


Seems the disk space is hidden in /dev/vda, so should I format it and mount it in order to
use that space? Thanks!

Cheers,
Dan


2015-03-13 10:41 GMT-05:00 Andrija Panic <andrija.panic@gmail.com>:

> I dont expect your partitions and file system will be resized here...
>
> give us     fdisk -l    and you should see bigger disk than original.
>
> Or maybe I'm wrong - some of the developers might confirm...we had 
> discussion about weather CS will also resize partition and FS - which 
> is I guess not the case...
>
> On 13 March 2015 at 16:36, Dan Dong <dongdan39@gmail.com> wrote:
>
> > Hi, All,
> >   I found when I create a new VM from a template, no matter how I 
> > set
> disk
> > offering, the created new VM always has the same original size. For 
> > Example, although I specified 100GB of hard disk, the actual disk 
> > size remains ~20GB, which should come with the template
> > itself:
> >
> > name = Large
> > id = a4d52dbd-abea-452f-a8e2-bc13c661f516
> > created = 2014-12-08T09:47:59-0600
> > disksize = 100
> > displayoffering = True
> > displaytext = Large Disk, 100 GB
> > iscustomized = False
> > storagetype = shared
> >
> > cloudmonkey deploy virtualmachine ...
> > diskofferingid=a4d52dbd-abea-452f-a8e2-bc13c661f516 ...
> >
> > ubuntu@node100GB:~$ df -h
> > Filesystem      Size  Used Avail Use% Mounted on
> > /dev/sda1       9.9G  762M  8.7G   8% /
> > none            4.0K     0  4.0K   0% /sys/fs/cgroup
> > udev            3.9G  4.0K  3.9G   1% /dev
> > tmpfs           799M  336K  799M   1% /run
> > none            5.0M     0  5.0M   0% /run/lock
> > none            3.9G     0  3.9G   0% /run/shm
> > none            100M     0  100M   0% /run/user
> >
> >  Is there a way to let the disk offering take effect?
> >
> > Cheers,
> > Dan
> >
>
>
>
> --
>
> Andrija Panić
>
Mime
View raw message