Hard Disk upgrade not showing up in WHM

[rijo.a]

Hello,

I have a vps (i guess xen) where it had around 160GB, i recently upgraded the hard disk to 20GB but the whm still shows the same size while fdsik shows around 180GB.

---------------
root@server [~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 158G 29G 563M 100% /

WHM shows the same output as the above command. There are no physical disks. It is a vps.
-----------

But df - H shows almost correct figures
root@server [~]# df -H
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 170G 160G 590M 100% /


-----------
Fdisk output
root@server [~]# fdisk -l

Disk /dev/xvda1: 171.8 GB, 171798691840 bytes -
255 heads, 63 sectors/track, 20886 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/xvda2: 7516 MB, 7516192768 bytes --- /dev/xvda2 is swap
255 heads, 63 sectors/track, 913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
--------------

Any help will be appreciated.

 

[rijo.a]

Nobody seen this error ? I saw similar post now after searching hours through the forum but didnt post any fix.
http://forums.cpanel.net/f5/whm-shows-disk-space-80gb-when-true-space-150gb-329502.html#post1344232

 

[cPanelMichael]

Hello

This sounds more like an issue with your VPS software as opposed to an issue with cPanel. Have you tried restarting your VPS?

Thank you.

 

[rijo.a]

Yes performed a system reboot but still its show old disk space and not updating in WHM or in df -h. I guess cpanel has nothing to do with it as df -h shows the same old readings while df -H shows correct. Any idea on the issue will be helpful to me.

 

[cPanelMichael]

I recommend consulting with the support of your VPS software application to see if there are any steps you can take to resolve this issue. Or, if you do not have access to the VPS node itself, contact your VPS hosting provider for assistance.

Thank you.