Proxmox dashboard readings missleading

[Moreiq]

I have two VM running on 256 SSD ZFS RAID 1. When looking on to Datacenter dashboard HDD size makes sense, but when looking in to PVE storage things are getting complicated to understand.

For example local-zfs-pve with total disk size 130GB holds 2 VM total size 175GB ???

Any suggestion how I shall read the size of the disks ?

 

[dcsapak]

what does 'zfs list' say?

 

[Moreiq]

NAME USED AVAIL REFER MOUNTPOINT
rpool 205G 21.5G 104K /rpool
rpool/ROOT 93.6G 21.5G 96K /rpool/ROOT
rpool/ROOT/pve-1 93.6G 21.5G 93.6G /
rpool/data 107G 21.5G 96K /rpool/data
rpool/data/vm-100-disk-2 107G 21.5G 107G -
rpool/data/vm-101-disk-1 482M 21.5G 482M -
rpool/swap 4.25G 22.1G 3.69G -

 

[dcsapak]

rpool/data 107G 21.5G 96K /rpool/data

total size is USED (107G) + AVAIL (21.5G) = 128.5 for VMs/Containers

rpool/ROOT/pve-1 93.6G 21.5G 93.6G /

USED (93.6G) + AVAIL (21.5G) = 115.1G for / (root)

 

[Moreiq]

Thanks for your reply. I have created 2 VMs. One 170gb disk size and another 5. During proxmox install I left 20gb for root. So how come now i have these crazy split ?

 

[dcsapak]

uring proxmox install I left 20gb for root.

with zfs there is no option to limit root

root and data share the whole space
where the total foreach is always : used+avail
while avail is the available space for the whole zpool

by default the zfs storage plugin is marked 'sparse' (thin provision in the gui) which makes the vm images use only the space they actually use (instead of how much you allocated) while still limiting their size

 

[Moreiq]

So if more space will be needed, that zfs will do proper allocation ?

 

[dcsapak]

So if more space will be needed, that zfs will do proper allocation ?

what do you mean? you have 21.5GB left free, if that is gone (be it on '/' or in a vm) your drive is full

 

[Moreiq]

I have a drive 256GB. Lets assume I use 10GB for Proxmox install and 20GB free. This leaves me with at least some 210GB of free disk space. On top of it I have 3 VM - 170GB -5GB - 9 GB = 185GB so some 25 GB shall be still available. However I have only 3GB

root@pve:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 223G 3.23G 104K /rpool
rpool/ROOT 91.7G 3.23G 96K /rpool/ROOT
rpool/ROOT/pve-1 91.7G 3.23G 91.7G /
rpool/data 127G 3.23G 96K /rpool/data
rpool/data/vm-100-disk-2 123G 3.23G 123G -
rpool/data/vm-101-disk-1 482M 3.23G 482M -
rpool/data/vm-102-disk-1 3.71G 3.23G 3.71G -
rpool/swap 4.25G 3.89G 3.59G -

 

[Moreiq]

Today I have recreated new VM from scratch. All working well, however now when doing VM backup on to attached USB drive my local-zfs(pve) is also getting filled up ???

 

[dcsapak]

Lets assume I use 10GB for Proxmox install and 20GB free.

this does not make sense since you cannot choose a root size if you choose zfs

root@pve:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 223G 3.23G 104K /rpool
rpool/ROOT 91.7G 3.23G 96K /rpool/ROOT
rpool/ROOT/pve-1 91.7G 3.23G 91.7G /
rpool/data 127G 3.23G 96K /rpool/data
rpool/data/vm-100-disk-2 123G 3.23G 123G -
rpool/data/vm-101-disk-1 482M 3.23G 482M -
rpool/data/vm-102-disk-1 3.71G 3.23G 3.71G -
rpool/swap 4.25G 3.89G 3.59G -

this says:

your root ('/') has 91.7 GiB of data
the disk of vm 100 has 123GiB of data
the disk of vm 101 has 482MiB of data
the disk of vm 102 has 3.71GiB of data
and the swap uses 4.25GiB

sum is ~223GiB used with a total size of ~227GiB give a free amount of 3.23GiB

All working well, however now when doing VM backup on to attached USB drive my local-zfs(pve) is also getting filled up ???

i am guessing the backups get written on the root instead of the usb drive ? how is the usb drive mounted and what storage do you select (storage.cfg)?

 

[Moreiq]

Thanks for following my post.

USB drive is mounted on /media/usb/

I have created under datacenter>storage>BackProxmox entry and backup selecting this location.

However now I realize that it might actually backup on /usb/ folder which means local drive and that is the issue. Nevertheless I have found a way to upload backups to dropbox so the matter has been resolved.