[SOLVED] pvesm add - ZFS error: dataset does not exist (500)

[Koleon]

Hello Proxmox team,

Recently, I've been learning more about the Proxmox VE Storage Manager and other Proxmox internal commands.
I was curious about how to create a dataset using the pvesm command instead of WebUI.

Firstly, I created a dataset on my ZFS pool, added it via Datacenter > Storage > Add > ZFS, and filled in all the details. Then I checked the /etc/pve/storage.cfg showing:

zfspool: nc-data
        pool rpool/ncdata
        blocksize 12k
        content rootdir,images
        mountpoint /rpool/nc-data
        sparse 1

On the other hand, adding the same storage using pvesm add zfspool nc-data --pool rpool/ncdata --content rootdir,images --sparse true --blocksize 12k creates:

zfspool: nc-data
        pool rpool/ncdata
        blocksize 12k
        content rootdir,images
        sparse 1

The missing mountpoint settings cause "zfs error: cannot open 'rpool/ncdata': dataset does not exist (500)" in WebUI. Is this a bug or feature? As the first method - creating the storage via WebUI does not ask for a mountpoint path.

 

[dakralex]

This looks strange indeed. A ZFS pool should usually be able to determine the mountpoint with the output of zfs get mountpoint <dataset>. What is the output of this command for rpool/ncdata on your machine? What is the output of zfs list? And is there a reason that the mountpoint /rpool/nc-data includes a dash opposed to the dataset name rpool/ncdata?

 

[Koleon]

Hi @dakralex ,
thank you for your prompt reply. Honestly, I checked it again and the rpool/ncdata is actually a typo that I didn't see before. I'm sorry about that, but once I tried it with correct parameter --pool rpool/nc-data the container was created as expected without the error message.