[SOLVED] ZFS not seeing VM, only CT volumes

[oldfart]

I have zfs storage

root@pve:/# zfs list
NAME                     USED  AVAIL     REFER  MOUNTPOINT
rpool                   3.34G   220G      104K  /rpool
rpool/ROOT              3.29G   220G       96K  /rpool/ROOT
rpool/ROOT/pve-1        3.29G   220G     3.29G  /
rpool/data                96K   220G       96K  /rpool/data
tank                     524G  3.01T      149K  /tank
tank/subvol-103-disk-0   436M  49.6G      436M  /tank/subvol-103-disk-0
tank/subvol-104-disk-0   775M  79.2G      775M  /tank/subvol-104-disk-0
tank/subvol-105-disk-0  3.81G  76.2G     3.81G  /tank/subvol-105-disk-0
tank/subvol-207-disk-0   393M  79.6G      393M  /tank/subvol-207-disk-0
tank/vm-100-disk-0      54.6G  3.05T     6.20G  -
tank/vm-210-disk-0       109G  3.08T     37.0G  -
tank/vm-214-disk-0       136G  3.13T     11.2G  -
tank/vm-215-disk-0      54.6G  3.06T     1.53G  -
tank/vm-216-disk-0       109G  3.11T     5.99G  -
tank/vm-220-disk-0      54.6G  3.06T     1.53G  -

root@pve:/# ls -a tank
.  ..  subvol-103-disk-0  subvol-104-disk-0  subvol-105-disk-0  subvol-207-disk-0

looks like Proxmox is attaching VM files at block level, not at directory
so, how do I mount those??

/etc/pve/storage.cfg
dir: local
    path /var/lib/vz
    content vztmpl,backup,iso


zfspool: local-zfs
    pool rpool/data
    content images,rootdir
    sparse 1


zfspool: tank
    pool tank
    content rootdir,images
    mountpoint /tank
    nodes pve

 

[leesteken]

looks like Proxmox is attaching VM files at block level, not at directory

That's correct. It uses zvols.

so, how do I mount those??

It depends on whether the block volume (the virtual disk) also has a partition table, in which case it needs an offset to the loop device.

 

[oldfart]

Solved - see https://forum.proxmox.com/threads/vzdump-problem.137975/