We don't use lvm inside containers here because we find out that is easier to resize without it.
You can even boot up with an GParted ISO that's makes very simple resizing the VM (even the client can do it) with very small risk comparing to use manual tools. - - - - - - - - - - - - - - - - - - - Rodrigo Baldasso - LHOST (51) 9 8419-9861 - - - - - - - - - - - - - - - - - - - On 03/08/2017 10:41:00, Imran Ahmed <im...@eaxiom.net> wrote: Hi Erik, Thanks for suggestion, I tried this too and was successful till lvextending the logical volume. However at the stage of running resize2fs it produced errors like : Bad super block..." so I ended up installing from an ISO and partitioning without LVM this time so that I could use this template to resize in future. Cheers, Imran -----Original Message----- From: Erik Weber [mailto:terbol...@gmail.com] Sent: Thursday, August 03, 2017 3:56 PM To: users@cloudstack.apache.org Subject: Re: Instance with a larger disk size then Template A faster approach than those mentioned is to create a new partition on the unused disk space, and add it to the volume group, then use lvextend and resizing the fs. On Thu, Aug 3, 2017 at 12:00 PM, Imran Ahmed wrote: > Hi All, > > I am creating an instance with a 300GB disk from a CentOS 7 template that > has 5GB disk (LVM Based). > The issue is that the root LVM partition inside the new VM instance still > shows 5GB . > > The device size (/dev/vda) however shows 300GB. The question is what is > the best strategy to resize the root LVM partition so that I could use all > 300G. > > Kind regards, > > Imran >
