I recently resized the hard drive of a VM from 150 GB to 500 GB in VMWare ESXi. After doing this, I used Gparted to effectively resize the partition of this image. Now all I have to do is to resize the file system, since it still shows the old value (as you can see from the output of df -h):
Filesystem Size Used Avail Use% Mounted on /dev/mapper/owncloud--vg-root 157G 37G 112G 25% / udev 488M 4.0K 488M 1% /dev tmpfs 100M 240K 100M 1% /run none 5.0M 0 5.0M 0% /run/lock none 497M 0 497M 0% /run/shm /dev/sda1 236M 32M 192M 14% /boot
However, running sudo resize2fs /dev/mapper/owncloud--vg-root returns this:
resize2fs 1.42 (29-Nov-2011) The filesystem is already 41608192 blocks long. Nothing to do!
Since Gparted says that my partition is /dev/sda5, I also tried running sudo resize2fs /dev/sda5, but in this case I got this:
resize2fs 1.42 (29-Nov-2011) resize2fs: Device or resource busy while trying to open /dev/sda5 Couldn't find valid filesystem superblock.
Finally, this is the output of pvs:
PV VG Fmt Attr PSize PFree /dev/sda5 owncloud-vg lvm2 a- 499.76g 340.04g
fdisk -l /dev/sda shows the correct amount of space.
How can I resize the partition so that I can finally make the OS see 500 GB of hard drive?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
Thanks a lot for @Bratchley answer and the comments. It helped me 🙂
My environment: Ubuntu 18.04 in VirtualBox 6.1
My case: I created 10GB fixed VDI disk and increased to 30GB dynamic using VirtualBox GUI. But still the increased space is not available to filesystem. Then came across @Bratchley answer.
Steps I ran:
- Run below command to get PV (Physical Volume) name (Ex:
/dev/sda1)
sudo pvs
- Resize the PV
sudo pvresize /dev/sda1
- Run below command to get root logical volume name (Filesystem value of
/row; ex:/dev/mapper/ubuntu--vg-root)
df -h
- Expand logical volume:
sudo lvextend -r -l +100%FREE /dev/mapper/ubuntu--vg-root
Method 2
If you only changed the partition size, you’re not ready to resize the logical volume yet. Once the partition is the new size, you need to do a pvresize on the PV so the volume group sees the new space. After that you can use lvextend to expand the logical volume into the volume group’s new space. You can pass -r to the lvextend command so that it automatically kicks off the resize2fs for you.
Personally, I would have just made a new partition and used vgextend on it since I’ve had mixed results with pvresize.
Method 3
This happened to me too, I have checked /etc/fstab and than I realized that I have renamed the VG and this did not change everywhere that rename, I was able to solve this by renaming back my VG!
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0