Hi,
I've just set up a 3-node testing cluster running PVE 5.2 and ran into some errors related to zfs storage with LXC containers. I had to install PVE over a debian stretch install due to my hardware being too old for GPT partitions. As part of the setup, I created a zpool (named tank) to store my VM and container data to enable migration. Being used to FreeNAS, I moved the zpool mountpoint to /mnt/tank instead of the default /tank with
On the VM side, everything is working fine. Migration (offline, online with local disks) works flawlessly. But when I try to create an LXC container on the zfs storage, there is an error:
The problem disappears when I set the mountpoint of the zpool to its default value (/tank).
Can anybody confirm if this is also an issue with the PVE iso install and that changing zfs mountpoints is not currently supported? Or is this just a result of my unconventional set up?
I've just set up a 3-node testing cluster running PVE 5.2 and ran into some errors related to zfs storage with LXC containers. I had to install PVE over a debian stretch install due to my hardware being too old for GPT partitions. As part of the setup, I created a zpool (named tank) to store my VM and container data to enable migration. Being used to FreeNAS, I moved the zpool mountpoint to /mnt/tank instead of the default /tank with
Code:
zfs set mountpoint=/mnt/tank tank
Code:
mounting container failed
TASK ERROR: cannot open directory //tank: No such file or directory
Can anybody confirm if this is also an issue with the PVE iso install and that changing zfs mountpoints is not currently supported? Or is this just a result of my unconventional set up?