Linux VM ( Debian ) keeps growing in disk size

depechie

New Member
Dec 7, 2024
10
1
3
I configured a Debian VM with 64GB of disk size.
It is running docker with Portainer hosted and 4 docker containers.
But what I notice is that the disk usage keeps increasing and I just needed to adjust the system to expand the disk to 128GB.
After reboot the `df -h /` shows a usage of 85GB.

So my question, how can I track down what is causing the huge jumps in disk size usage?
 
So my question, how can I track down what is causing the huge jumps in disk size usage?

Depending on your tooling Docker might pull updated images without deleting old ones.

Check with docker images. Use docker image prune to radically clean up - after first creating a snapshot of the VM, "prune", rebooting and veryifying that everything works still fine you can remove the snapshot to reclaim free space. This approach is usually quicker than restoring from backup.

Btw... this is not really PVE specific, right? ;-)
 
  • Like
Reactions: leesteken
Hey @UdoB thx for the reply already... I know it is not strictly Proxmox. But I had my Intel NUC running only Debian with docker for a few years and recently I reinstalled it but with Proxmox as main OS and now hosting a few LXC's and 2 Debian VM's.

And what I never had with the Debian as main OS now happening with the Debian as virtual VM, that the disk keeps allocating more size :/

All the virtual resources have total allocated size equal to 195GB and below you see that the disk usage is not 100% even ( per resource ).

Screenshot 2025-04-12 at 14.47.28.png
Screenshot 2025-04-12 at 15.08.13.png
Screenshot 2025-04-12 at 14.48.35.pngScreenshot 2025-04-12 at 14.49.05.png
 
Last edited:
Although the 500GB drive is already at 97%, that is something I do not understand from a proxmox perspective.
You have given nvme0n1p3 as a "Physical Extent" to LVM. From the top view nvme0n1p3 seem to be "full", but the LVM itself may still be empty (at the beginning).

"Slices" (Logical Volumes) are created when you configure a new VM or a container (not sure, I do not use LVM), using space inside that "Volume Group". I am very sure this is described somewhere, so I won't repeat it from scratch here. Some information is in the Wiki: https://pve.proxmox.com/wiki/Storage:_LVM and while PVE is based on Debian the Arch wiki is known for good quality articles: https://wiki.archlinux.org/title/LVM

Basically everything look fine..., but the problem of sparse volumes getting actually full does exist.

Again: I do not use LVM, I have no idea how and if "disk full" happens nowadays and how it is prevented with this technology. (ZFS has this problem too, but there I know what to do...)
 
  • Like
Reactions: depechie