ZFS mount with incorrect size

[bedas]

Hi,

i'm testing a ZFS configuration here, added a new 500GB drive and ZFS mounted it nicely in /zfs, but when I add it in the web GUI as a directory it shows the size of /dev/mapper/pve-root that is very small compared, and it doesn't allow me to create or restore backup into the zpool, even if upon creation of a VM in the "Content" area it shows the correct size for the image..

also at the very beginning I've copied some files into the zpool that just disappeared, I believe when I removed and add it up again in "Datacenter > Storage". however when I run #zfs list , it shows correctly the used space for those files and the remainder to the 500GB

any hint..?

 

[Nemesiz]

I believe when I removed and add it up again in "Datacenter > Storage". however when I run #zfs list , it shows correctly the used space for those files and the remainder to the 500GB

First check does zfs is mounted.

zfs get mounted

Hi,

i'm testing a ZFS configuration here, added a new 500GB drive and ZFS mounted it nicely in /zfs, but when I add it in the web GUI as a directory it shows the size of /dev/mapper/pve-root that is very small compared, and it doesn't allow me to create or restore backup into the zpool, even if upon creation of a VM in the "Content" area it shows the correct size for the image..

The same above. To work ZFS and PROXMOX together you must do some work too. After you add directory to storage you must be sure ZFS starts before pvestatd on boot.

 

[bedas]

thanks for the hint, that is the issue.

I was confident that ZFS automounts the filesystem so I didn't even checked. mountall didn't install for some broken dependencie, libplymouth I think. I'm gonna bang my head little more over this.

Thanks

 

[bedas]

SOLVED

just needed to change a config file in /etc/default/zfs and set ZFS_MOUNT and ZFS_UMOUNT to 'yes'

it goes automatically to start before pvestatd

thanks again for the heads up
cheers