We have this issue long time ago. We manually resize root when VM's still running. After resize and reboot the size show correct.
On Aug 4, 2017 6:25 AM, "ilya" <[email protected]> wrote: > Just a thought - as i do this very frequently. > > If you are using LVM on your ROOT partition - you dont need to power it > on via Live CD. > > It can all be done online while the system running. > > > > > On 8/3/17 6:40 AM, Imran Ahmed 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:[email protected]] > > Sent: Thursday, August 03, 2017 3:56 PM > > To: [email protected] > > 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 <[email protected]> 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 > >> > > >
