Can not scan/find folder of ZFS local array

First and foremost consider this:

• Only RetroArch bugs should be filed here. Not core bugs or game bugs
• This is not a forum or a help section, this is strictly developer oriented

Description

When selecting the scan directory option and selecting / my ZFS array is not found. I've been transferring files to it and have steam play games off of it, so it is not a hardware problem.

Expected behavior

The folder would appear like every other folder does.

Actual behavior

The folder is missing, like it doesn't exist.

Steps to reproduce the bug

1. have a ZFS array
2. launch (steam) Retroarch and scan directory option
3. go to where the ZFS array is on the system, and its visible.

Bisect Results

It has to be related to the ZFS filesystem and Retroarch. Roms anywhere else on the system are able to be scanned and played perfectly fine.

Using this drive as a network share on a Windows 10 machine loads the directories perfectly.

Version/Commit

You can find this information under Information/System Information

• RetroArch: Steam release as of Feb 26, 2023.

Environment information

• OS: Debian GNU/Linux 11 (bullseye)
• Kernel: 5.10.0-21-amd64

(the folder trying to be picked up is boundman)

Text Version:

redhawk@Paisley-Park:/$ ls -lah
total 99K
drwxr-xr-x  23 root    root    4.0K Feb 26 21:37 .
drwxr-xr-x  23 root    root    4.0K Feb 26 21:37 ..
lrwxrwxrwx   1 root    root       7 Feb 25 20:09 bin -> usr/bin
drwxr-xr-x   3 root    root    4.0K Feb 25 23:48 boot
drwxr-xr-x   4 redhawk redhawk    4 Feb 26 19:36 boundman
drwxr-xr-x   4 root    root    4.0K Feb 25 23:38 .cache
drwxr-xr-x   3 root    root    4.0K Feb 25 23:38 .config
drwxr-xr-x  18 root    root    3.5K Feb 26 22:12 dev
drwxr-xr-x 131 root    root     12K Feb 26 21:37 etc
drwxr-xr-x   3 root    root    4.0K Feb 25 20:25 home
lrwxrwxrwx   1 root    root      31 Feb 25 20:12 initrd.img -> boot/initrd.img-5.10.0-21-amd64
lrwxrwxrwx   1 root    root      31 Feb 25 20:10 initrd.img.old -> boot/initrd.img-5.10.0-10-amd64
lrwxrwxrwx   1 root    root       7 Feb 25 20:09 lib -> usr/lib
lrwxrwxrwx   1 root    root       9 Feb 25 20:09 lib32 -> usr/lib32
lrwxrwxrwx   1 root    root       9 Feb 25 20:09 lib64 -> usr/lib64
lrwxrwxrwx   1 root    root      10 Feb 25 20:09 libx32 -> usr/libx32
drwxr-xr-x   3 root    root    4.0K Feb 25 23:38 .local
drwx------   2 root    root     16K Feb 25 20:09 lost+found
drwxr-xr-x   4 root    root    4.0K Feb 25 21:03 media
drwxr-xr-x   2 root    root    4.0K Feb 25 20:09 mnt
drwxr-xr-x   3 root    root    4.0K Feb 25 23:35 opt
dr-xr-xr-x 356 root    root       0 Feb 26 21:36 proc
drwx------   4 root    root    4.0K Feb 25 20:40 root
drwxr-xr-x  32 root    root     860 Feb 26 22:28 run
lrwxrwxrwx   1 root    root       8 Feb 25 20:09 sbin -> usr/sbin
drwxr-xr-x   2 root    root    4.0K Feb 25 20:09 srv
dr-xr-xr-x  13 root    root       0 Feb 26 21:36 sys
drwxrwxrwt  17 root    root    4.0K Feb 26 22:08 tmp
drwxr-xr-x  14 root    root    4.0K Feb 25 20:09 usr
drwxr-xr-x  11 root    root    4.0K Feb 25 20:09 var
lrwxrwxrwx   1 root    root      28 Feb 25 20:12 vmlinuz -> boot/vmlinuz-5.10.0-21-amd64
lrwxrwxrwx   1 root    root      28 Feb 25 20:10 vmlinuz.old -> boot/vmlinuz-5.10.0-10-amd64
drwxr-xr-x   2 root    root       0 Dec 31  1969 zfs-kstat

Image:

Start at RetroArch's Scan Directory option and reproduce the missing boundman folder on Debian 11 with the reported ZFS setup. Compare directory visibility and scanning behavior with a filesystem that already works, then verify that the folder appears and its ROMs can be scanned and played.