Virtualmin not seeing new/correct disk-size - how to fix?

OS type and version Debian 7
Webmin version 1.991
Virtualmin version 6.17-3
Related packages proxmox VE

Virtualmin 6.17-3 on a proxmox VE w. a Debian 7.

Disk had run full and was extended via proxmox gui.

VE was rebooted.

New disk size shows in console:

Filesystem      Size  Used Avail Use% Mounted on
/dev/loop1      108G   68G   36G  66% /
none            492K  4.0K  488K   1% /dev
none            1.6G  224K  1.6G   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            7.8G     0  7.8G   0% /run/shm
none            100M     0  100M   0% /run/user

…but Virtualmin doesn’t “see” or recognise the new disk size, still thinks it has only 68Gig (which are full):

Warning! The 68.65 GiB filesystem mounted at / has no free disk space!

Interestingly, it also thinks it has a System uptime of 595 days, 22 hours, 36 minutes, even though it was just rebooted:

# uptime 13:06:45 up 1:03, 0 users, load average: 2.90, 2.41, 1.87

Q: how can we tell virtualmin, that it now got 20GB more space?
Or: (How) does virtualmin update the available disk-space?

P.S. yes, we should update to a newer versions, but update failed and - except for the disk-space-issue described here - box runs fine and had a ~600 days uptime:

The following packages have unmet dependencies: virtualmin-config : Depends: perl:any but it is not installable E: Unable to correct problems, you have held broken packages.

I don’t think Virtualmin can do this. Have you read Resize disks - Proxmox VE


As outlined above, Steve, disk WAS resized via proxmox.
I added 20GB (see ‘df’ above), rebooted but virtualmin doesn’t see/realize it… :man_shrugging:t3:
Also there is no Quota and all User-Limits are set to “Unlimited”…

…but to be 200% sure, I added another 10GB - same symptoms, even though there is plenty of space:

:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop0      118G   67G   45G  60% /
none            492K  8.0K  484K   2% /dev
none            492K  8.0K  484K   2% /proc/sys/kernel/random/boot_id
none            381M  224K  380M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            1.9G     0  1.9G   0% /run/shm
none            100M     0  100M   0% /run/user
:~# df -ih
Filesystem     Inodes IUsed IFree IUse% Mounted on
/dev/loop0       7.5M  453K  7.1M    6% /
none             476K    61  476K    1% /dev
none             476K    61  476K    1% /proc/sys/kernel/random/boot_id
none             476K   107  476K    1% /run
none             476K     2  476K    1% /run/lock
none             476K     2  476K    1% /run/shm
none             476K     1  476K    1% /run/user

Never had this issue. I found this in the forum. Maybe is a issue with Debian version.
Its a unsupported OS. Virtualmin OS Support – Virtualmin

The box I am talking about is Debian 7, not 11 (unfortunately)

yep, Debian 7 is not listed either, just a thought why it seems broke.


well, it works on another box w. exactly the same setup.
Can s.o. here confirm, that webmin 1.991 and Virtualmin 6.17-3 do not work w. Debian 7?
If so: why do webmin and Virtualmin update themselves to these versions on a Deb7?

Being not support doesn’t mean it won’t work, but changes to virtualmin might cause issue with unsupported OS, it maybe whats happened here. You need to ask Joe or one of the other staff to confirm.