Say what?? This is precisely what
resize2fs are for. We even use them to resize mounted root on a running system.
Let’s get our terminology settled, at least:
Volume - The “Disk” (real or virtual) attached to your VMware instance (VMware calls them “Hard Disks”)
Partition - The divisions/boundaries for differing file systems within the Volume.
File System - The logical “format” of the directory and file structure within the Partition…in this case, ext2
If your Volume is 250GiB but your Partition is only 50GiB, then that Partition will only be able to house a 50GiB File System. If you started out with a Partition the same size as your Volume, then resize your Volume with VMware, the Partition will not automatically resize with it. That’s what
growpart is for. Using
growpart will not resize the File System when it resizes the Partition. That’s what
resize2fs is for. So, if you started with a 50GiB Volume, 50GiB Partition, and 50GiB File System but then wanted to make that 250GiB, you would:
- from within VMware, resize Volume
- from within the OS, resize Partition with
- resize File System with
growpart can be installed via EPEL repos
yum install cloud-utils-growpart
I do agree that we need to know mount/disk info. We can see everything we need (mounts and sizes/free space) if one runs