One of the servers I’m working with started running out of disk space recently. The machine is running on a Ubuntu VM in Windows, about 200 miles from my desk. I have remote access to the VM, but I don’t have access to the virtualization software. After requesting a disk resize through the IT company that manages our Windows network, here’s what I saw:
1 2 3 4 |
|
The request I made was to increase the disk space from 14G to ~40G. That additional space doesn’t show up, as it’s free space on the disk (it hasn’t yet been assigned to a volume). Running the vgdisplay
will show the additional space (Free PE / Size):
1 2 3 4 5 6 |
|
So, the disk was expanded, however I needed to assign that free space to /dev/mapper/outlays-root … I wasn’t sure how. A bit of Googling brought me to this article: Extending LVM disks in Linux using VMWare virtual disks. The solution seemed to be to extend the /dev/mapper/outlays-root by the amount of freespace available in the volume group. First, I wanted to check out the /dev/mapper/outlays-root disk:
1 2 3 4 5 6 7 8 |
|
And running the lvdisplay
command shows the following:
1 2 3 4 5 6 |
|
So, the assumption I made here was the /dev/mapper/outlays-root maps to /dev/outlays/root. Alright, I needed to expand /dev/outlays/root. Expanding the disk was as simple as running the following commands:
1
|
|
1
|
|
Now, here’s the amount of disk space I have:
1 2 3 4 |
|
Much better.