Bootdisk size not showing in Summary and VM acts as if the disk is full (no upgrades allowed)

[marcor78]

As per the title.... I don't know exactly when it occurred, but I noticed that my 2 VMs are not showing Bootdisk size in Summary and they behave as the disk is full (when I believe it is not). Therefore no upgrades are possible (impossible to write on the disk as it seems full). Here are a snapshot of VM summary and my pveversion.
How can I debug this issue?

# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-6
pve-kernel-helper: 7.0-6
pve-kernel-5.4: 6.4-4
pve-kernel-5.0: 6.0-11
pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.11.22-1-pve: 5.11.22-2
pve-kernel-5.11.0-1-pve: 5.11.0-1
pve-kernel-5.10.6-1-pve: 5.10.6-1
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.78-1-pve: 5.4.78-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 14.2.21-1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

 

[Republicus]

As I see it your PVE is reporting a bootdisk size in the summary. I see an 8 GiB bootdisk in the provided screen capture.

Are you expecting a different size? Without knowing the guest OS all I can suggest is you verify the disk and its usage within the guest.

 

[marcor78]

As I see it your PVE is reporting a bootdisk size in the summary. I see an 8 GiB bootdisk in the provided screen capture.

Are you expecting a different size? Without knowing the guest OS all I can suggest is you verify the disk and its usage within the guest.

Sorry, I should have explained better: the bootdisk size is correct, I simply don't see usage % anymore. And if I try to make upgrades within the guest it says "not enough space in disk", but this is not true, according to lvs -a as following (the disk is vm-114-disk-0):

# lvs -a
  LV              VG  Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data            pve twi-aotz-- 60.66g             77.38  3.83                           
  [data_tdata]    pve Twi-ao---- 60.66g                                                   
  [data_tmeta]    pve ewi-ao----  1.00g                                                   
  [lvol0_pmspare] pve ewi-------  1.00g                                                   
  root            pve -wi-ao---- 27.75g                                                   
  swap            pve -wi-ao----  7.00g                                                   
  vm-100-disk-0   pve Vwi-aotz--  4.00m data        0.00                                   
  vm-100-disk-1   pve Vwi-aotz-- 32.00g data        77.53                                 
  vm-107-disk-1   pve Vwi-aotz--  8.00g data        79.25                                 
  vm-111-disk-0   pve Vwi-aotz--  8.00g data        67.69                                 
  vm-114-disk-0   pve Vwi-aotz--  8.00g data        87.70                                 
  vm-115-disk-1   pve Vwi-aotz--  5.00g data        67.20

 

[Republicus]

Im not sure if VMs ever showed disk usage? I am on PVE v6.4 and do not see my virtual machines' bootdisk usage from within PVE -- that is with or without the guest tools installed within the VM. Containers, on the other hand, will show that info in PVE.

What is the guest OS in that VM?
All of those disks are fairly filled. Check the usage from within the VM.
That disk may partitioned and space used differently than you expect.

 

[marcor78]

Im not sure if VMs ever showed disk usage? I am on PVE v6.4 and do not see my virtual machines' bootdisk usage from within PVE -- that is with or without the guest tools installed within the VM. Containers, on the other hand, will show that info in PVE.

What is the guest OS in that VM?
All of those disks are fairly filled. Check the usage from within the VM.
That disk may partitioned and space used differently than you expect.

The guest OS is Debian Buster and there's Docker installed on it.
This is the df command within the VM:

# df
File system    1K-blocchi   Usati Disponib. Uso% Montato su
udev              1490008       0   1490008   0% /dev
tmpfs              300976    4340    296636   2% /run
/dev/sda1         7158264 7124376         0 100% /
tmpfs             1504868       0   1504868   0% /dev/shm
tmpfs                5120       0      5120   0% /run/lock
tmpfs             1504868       0   1504868   0% /sys/fs/cgroup
overlay           7158264 7124376         0 100% /var/lib/docker/overlay2/0d710c308f160d0ae407054345d0e301b884b3e4f6a7fe247426101c645a8fdf/merged
shm                 65536    8556     56980  14% /var/lib/docker/containers/c8522c241457a870928d7f90faaeb93ae6553284148de293de7a0f6bc7dcfb93/mounts/shm
tmpfs              146964       0    146964   0% /run/user/0

I also resized the disk adding 2 more GB. It is now 10GB instead of 8GB, but nothing changes and if I run "df" after resizing the result is still the same as before.... I really don't know where this space has gone.... it seems like the VM is not able to properly read the space available?

 

[DST73]

Hi,

any update to this? I have the same behavior running an ubuntu 24 vm where the summary only shows the (correct) size but not how much of it is used.