Missing path to ZFS pool in /dev/ dir after recent updates

[Donner]

Hi, i noticed that after recent updates there no path like /dev/<zfspoolname> anymore. Is there way to fix it?
I'm using proxmox host also like a storage for ZFS over iSCSI (LIO) and it seems this feature uses paths like /dev/<zfspoolname>/<zvol> that's not working any more.

 

[UdoB]

I am not really sure what you are looking for (as '.../<vdev>' makes no sense) but I can find the virtual disks of my systems here: /dev/zvol/<poolname>/<datasetname>/

Those are links to /dev/zd<xyz>...

Added Example: this works for all ZVol, not only "official" virtual disks:

~# zfs list -t volume
NAME                        USED  AVAIL  REFER  MOUNTPOINT
rpool/data/vm-1177-disk-0  22.5G   981G  4.16G  -

~# ls -al /dev/zvol/rpool/data/vm-1177-disk-0
lrwxrwxrwx 1 root root 13 Dec  7 14:17 /dev/zvol/rpool/data/vm-1177-disk-0 -> ../../../zd32

 

[Donner]

I am not really sure what you are looking for (as '.../<vdev>' makes no sense) but I can find the virtual disks of my systems here: /dev/zvol/<poolname>/

for example: TASK ERROR: Could not open /dev/dRAID3/vm-122-disk-0

zpool is ok and vm-122-disk-0 too, just missing that path.
I have several nodes, not all updated yet, so i was seeing that there was "/dev/NVMe" (pool name) before update and restart, and now it gone, only that path, the pool still works fine.

EDITED - zvol, not vdev.

 

[Donner]

Added Example: this works for all ZVol, not only "official" virtual disks:

~# zfs list -t volume
NAME                        USED  AVAIL  REFER  MOUNTPOINT
rpool/data/vm-1177-disk-0  22.5G   981G  4.16G  -

~# ls -al /dev/zvol/rpool/data/vm-1177-disk-0
lrwxrwxrwx 1 root root 13 Dec  7 14:17 /dev/zvol/rpool/data/vm-1177-disk-0 -> ../../../zd32

I cant do something with it, that pattern like /dev/<zfspoolname>/<zvol> is hardcoded in ZFSoiSCSI storage client. So thats pussibly a bug if there no way to restore old path way

 

[UdoB]

...hardcoded in ZFSoiSCSI storage client. So thats pussibly a bug

As I do not use this mechanism I can not verify this. If you are convinced that this is actually a bug you may report it via https://bugzilla.proxmox.com/ to make the developers aware of it. (While staff members do thankfully support us here "bugzilla" is the official place to report bugs.)

A brutal workaround could be to create those missing links manually. While this feels wrong it may (or may not) work.

 

[Donner]

As I do not use this mechanism I can not verify this. If you are convinced that this is actually a bug you may report it via https://bugzilla.proxmox.com/ to make the developers aware of it. (While staff members do thankfully support us here "bugzilla" is the official place to report bugs.)

A brutal workaround could be to create those missing links manually. While this feels wrong it may (or may not) work.

Ah, find one already https://bugzilla.proxmox.com/show_bug.cgi?id=5071
so, will waiting for fix