[EZFS_INVALIDNAME]: zfs_open() failed - cannot open ‘Storage/ShadowShare/[P3]’: invalid character ‘[’ in name
(Storage/ShadowShare is a dataset, [P3] is a folder name.)
I get this error on Datasets page after updating to 25.10.
Rollback to 25.04 fixes the issue, but it’s still not something good.
Are you sure? ZFS is only concerned with datasets, not folders.
Can you confirm.
zfs list -t fs -r Storage
root@truenas[~]# zfs list -t fs Storage -r
NAME USED AVAIL REFER MOUNTPOINT
Storage 17.0T 13.9T 749M /mnt/Storage
Storage/.ix-virt 9.96G 13.9T 205K legacy
Storage/.ix-virt/buckets 205K 13.9T 205K legacy
Storage/.ix-virt/containers 205K 13.9T 205K legacy
Storage/.ix-virt/custom 9.95G 13.9T 205K legacy
Storage/.ix-virt/deleted 1.20M 13.9T 205K legacy
Storage/.ix-virt/deleted/buckets 205K 13.9T 205K legacy
Storage/.ix-virt/deleted/containers 205K 13.9T 205K legacy
Storage/.ix-virt/deleted/custom 205K 13.9T 205K legacy
Storage/.ix-virt/deleted/images 205K 13.9T 205K legacy
Storage/.ix-virt/deleted/virtual-machines 205K 13.9T 205K legacy
Storage/.ix-virt/images 205K 13.9T 205K legacy
Storage/.ix-virt/virtual-machines 8.96M 13.9T 205K legacy
Storage/.ix-virt/virtual-machines/windows-dev 8.65M 491M 8.10M legacy
Storage/.system 8.08G 13.9T 1.66G legacy
Storage/.system/configs-5a0a2a47cd884dbcbe527966286bfc29 137M 13.9T 136M legacy
Storage/.system/cores 558M 466M 256K legacy
Storage/.system/ctdb_shared_vol 205K 13.9T 205K legacy
Storage/.system/glusterd 222K 13.9T 222K legacy
Storage/.system/netdata-5a0a2a47cd884dbcbe527966286bfc29 2.47G 13.9T 476M legacy
Storage/.system/nfs 896K 13.9T 299K legacy
Storage/.system/rrd-5a0a2a47cd884dbcbe527966286bfc29 72.3M 13.9T 72.3M legacy
Storage/.system/samba4 7.41M 13.9T 1.32M legacy
Storage/.system/services 205K 13.9T 205K legacy
Storage/.system/syslog-5a0a2a47cd884dbcbe527966286bfc29 66.3M 13.9T 66.3M legacy
Storage/.system/vm 213K 13.9T 213K legacy
Storage/.system/webui 205K 13.9T 205K legacy
Storage/Archive 164G 13.9T 133G /mnt/Storage/Archive
Storage/Backups 227G 13.9T 213K /mnt/Storage/Backups
Storage/Downloads 1.85T 13.9T 1.77T /mnt/Storage/Downloads
Storage/Home 580K 13.9T 358K /mnt/Storage/Home
Storage/Media 8.83T 13.9T 8.22T /mnt/Storage/Media
Storage/Personal 24.4G 13.9T 24.4G /mnt/Storage/Personal
Storage/Private 3.89G 13.9T 3.89G /mnt/Storage/Private
Storage/ShadowShare 5.72T 13.9T 5.68T /mnt/Storage/ShadowShare
Storage/Shared 1.70G 13.9T 1.70G /mnt/Storage/Shared
Storage/VM 1.48G 13.9T 1.48G /mnt/Storage/VM
Storage/docker 134G 13.9T 222K /mnt/Storage/docker
Storage/docker/data 134G 13.9T 132G /mnt/Storage/docker/data
Storage/docker/stacks 486K 13.9T 486K /mnt/Storage/docker/stacks
Storage/jailmaker 88.1G 13.9T 77.3M /mnt/Storage/jailmaker
Storage/jailmaker/jails 88.0G 13.9T 205K /mnt/Storage/jailmaker/jails
Storage/jailmaker/jails/docker 88.0G 13.9T 83.6G /mnt/Storage/jailmaker/jails/docker
I forgot to include vol and -o space.
zfs list -t fs,vol -r -o space Storage
I’m confused why the datasets page on the GUI would alert you to a folder name. The page for datasets should not have any awareness of folders in individual filesystems.
Can you generate a debug file on 25.10 (after reproducing the issue) and file a bug ticket?
I’m confused why the datasets page on the GUI would alert you to a folder name. The page for datasets should not have any awareness of folders in individual filesystems.
Which is the reason for the question in the first place
root@truenas[~]# zfs list -t fs,vol -r -o space Storage
NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD
Storage 13.8T 17.1T 324K 749M 0B 17.1T
Storage/.ix-virt 13.8T 9.96G 0B 205K 0B 9.96G
Storage/.ix-virt/buckets 13.8T 205K 0B 205K 0B 0B
Storage/.ix-virt/containers 13.8T 205K 0B 205K 0B 0B
Storage/.ix-virt/custom 13.8T 9.95G 0B 205K 0B 9.95G
Storage/.ix-virt/custom/default_en-us_windows_10_dvd_cf2250c6.iso.iso 13.8T 6.97G 34.1K 6.97G 0B 0B
Storage/.ix-virt/custom/default_linuxmint-22.1-cinnamon-64bit.iso.iso 13.8T 2.98G 34.1K 2.98G 0B 0B
Storage/.ix-virt/deleted 13.8T 1.20M 0B 205K 0B 1024K
Storage/.ix-virt/deleted/buckets 13.8T 205K 0B 205K 0B 0B
Storage/.ix-virt/deleted/containers 13.8T 205K 0B 205K 0B 0B
Storage/.ix-virt/deleted/custom 13.8T 205K 0B 205K 0B 0B
Storage/.ix-virt/deleted/images 13.8T 205K 0B 205K 0B 0B
Storage/.ix-virt/deleted/virtual-machines 13.8T 205K 0B 205K 0B 0B
Storage/.ix-virt/images 13.8T 205K 0B 205K 0B 0B
Storage/.ix-virt/virtual-machines 13.8T 8.96M 0B 205K 0B 8.76M
Storage/.ix-virt/virtual-machines/windows-dev 491M 8.65M 563K 8.10M 0B 0B
Storage/.ix-virt/virtual-machines/windows-dev.block 13.8T 119K 0B 119K 0B 0B
Storage/.system 13.8T 8.10G 3.13G 1.66G 0B 3.31G
Storage/.system/configs-5a0a2a47cd884dbcbe527966286bfc29 13.8T 137M 1024K 136M 0B 0B
Storage/.system/cores 466M 558M 558M 256K 0B 0B
Storage/.system/ctdb_shared_vol 13.8T 205K 0B 205K 0B 0B
Storage/.system/glusterd 13.8T 222K 0B 222K 0B 0B
Storage/.system/netdata-5a0a2a47cd884dbcbe527966286bfc29 13.8T 2.49G 2.00G 498M 0B 0B
Storage/.system/nfs 13.8T 896K 597K 299K 0B 0B
Storage/.system/rrd-5a0a2a47cd884dbcbe527966286bfc29 13.8T 72.3M 0B 72.3M 0B 0B
Storage/.system/samba4 13.8T 7.43M 6.12M 1.32M 0B 0B
Storage/.system/services 13.8T 205K 0B 205K 0B 0B
Storage/.system/syslog-5a0a2a47cd884dbcbe527966286bfc29 13.8T 66.3M 0B 66.3M 0B 0B
Storage/.system/vm 13.8T 213K 0B 213K 0B 0B
Storage/.system/webui 13.8T 205K 0B 205K 0B 0B
Storage/Archive 13.8T 164G 30.7G 133G 0B 0B
Storage/Backups 13.8T 227G 0B 213K 0B 227G
Storage/Backups/Theseus-Backups 13.8T 227G 34.1K 227G 0B 0B
Storage/Downloads 13.8T 1.86T 88.3G 1.77T 0B 0B
Storage/Home 13.8T 580K 222K 358K 0B 0B
Storage/Media 13.8T 8.83T 619G 8.22T 0B 0B
Storage/Personal 13.8T 24.4G 0B 24.4G 0B 0B
Storage/Private 13.8T 3.89G 7.23M 3.89G 0B 0B
Storage/ShadowShare 13.8T 5.72T 38.7G 5.68T 0B 0B
Storage/Shared 13.8T 1.70G 290K 1.70G 0B 0B
Storage/VM 13.8T 1.48G 0B 1.48G 0B 0B
Storage/docker 13.8T 134G 0B 222K 0B 134G
Storage/docker/data 13.8T 134G 2.24G 132G 0B 0B
Storage/docker/stacks 13.8T 486K 0B 486K 0B 0B
Storage/jailmaker 13.8T 88.1G 0B 77.3M 0B 88.0G
Storage/jailmaker/jails 13.8T 88.0G 0B 205K 0B 88.0G
Storage/jailmaker/jails/docker 13.8T 88.0G 4.39G 83.6G 0B 0B
I did. Hope it will do some good. NAS-138034
There’s new findings: NFS stopped working.
The service itself works, but shares list is empty. (starts working on rollback)
And yes, Storage/ShadowShare/[P3] is used as NFS share path.
That might be why.
Is it possible to stop the NFS service, remove the share that points to the [P3] folder, then rename the folder and redo the share?
You shouldn’t be using special characters in your folder or file names anyways.
It looks like the issue is with some edge case handling for detecting whether a share path is locked. We were handling EZFS_NOENT but not EZFS_INVALIDNAME. In 25.10 we’re transitioning from our old pylibzfs library (not thread safe) to a new libzfs python library that is thread-safe (allowing us to gradually eliminate using a process pool). The result is that the backend is much faster / reliable, but we will have a few wrinkles to iron out here and there.
Being backported for 25.10.0
You shouldn’t be using special characters in your folder or file names anyways.
Thanks but I’ll keep using them. I suppose I’ll have to wait for the fix. Regression is a regression.
Looks like a good time to add a test for unusual file and directory names. This test is for automated release testing, not in code testing. If something like this was in place, it may have caught this regression bug.