Proxmox 3.1-21 Disk usage OpenVz show containers 0.0 % in use !?? Bug ? Or ?

ictdude

Renowned Member
May 18, 2008
88
0
71
Proxmox 3.1-21 Proxmox 3.1-21 Disk usage OpenVz show containers 0.0 % in use !?? Bug ? Or ? While disk do use some space. Also in webmin console disk use 0.0 % Is this different then 2.3-13 ??? Is this a option you must activate ? Is there a lot different between Version 2.3-13 and 3.1-21 ?
 
Proxmox 3.1-21 Proxmox 3.1-21 Disk usage OpenVz show containers 0.0 % in use !?? Bug ? Or ? While disk do use some space. Also in webmin console disk use 0.0 % Is this different then 2.3-13 ??? Is this a option you must activate ?

difficult to say with no details. I guess there's no option involved...

Is there a lot different between Version 2.3-13 and 3.1-21 ?
quite a lot, but nothing totally different to be incompatible, afaik.

Marco
 
difficult to say with no details. I guess there's no option involved...


quite a lot, but nothing totally different to be incompatible, afaik.

Marco

Strange ? I just setup a Proxmox version 3. And did restore some Openvz containers from version 2.3. And the disk usage shows 0.0 %
Also new containers have this issue. While the proxmox host do show disk usage also the storage show correct disk use in %

nothing strange in the setup:


root@host235 ~ # pveversion -v

proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
 
Last edited:
Thank you. Seems like my problem is different, it's being shown as 0% even if the VMs are being started. And it's quemu, KVM, not OpenVZ.