Drastic Hard Drive Space Consumption - Please HELP


(bholler) #1

Hi Everyone,

My hard disk suddenly got filled up. Then I expanded the VM hard drive from 50GB to 500GB.

I followed this instruction - https://kb.vmware.com/s/article/1006371 to expand the file system.

Below is my Output when I run fdisk -l command

Disk /dev/sda: 536.9 GB, 536870912000 bytes, 1048576000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0002f16c

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 4098047 2048000 83 Linux
/dev/sda2 4098048 104857599 50379776 8e Linux LVM
/dev/sda3 104857600 1048575999 471859200 8e Linux LVM

Disk /dev/mapper/SangomaVG-root: 43.9 GB, 43905974272 bytes, 85753856 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/SangomaVG-swaplv1: 129.7 GB, 129654325248 bytes, 253231104 sector
s
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

The Confusion (when I run df -h / command):

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/SangomaVG-root 41G 32G 9.2G 78% /

Can someone explain why the actual size of /sda is not reflecting in the second command.

PLS HELP!!


(Sam Shomi) #2

Not the answer you are looking for but whenever I need to resize a partition, I always just use GParted

https://gparted.org/livecd.php


(bholler) #3

thank you for your reply.

I need to find a way to expand the root drive driver /SangomaVG-root.

In addition is there a way i can point the storage of the voice file (from the call recording) to /dev/sda3 ?

can anyone help me?


#4

When you followed that KB article, did you do all the steps and no errors were seen?

One thing I’m wondering (if you followed it exactly), what you used for the volume group as I believe one should use SangomaVG (not VolGroup00 used in the KB article) as it looks like you have a system installed from a fpbx distro.
And the example lvextend command would have /dev/SangomaVG/root as the argument, not the /dev/VolGroup00/LogVol00 used in the KB article.

What did you use?