Re: FreeBSD 16 nfsd: Unexpected NFS error 'NFS4ERR_NOFILEHANDLE' while probing named attr support

On Tue, Mar 10, 2026 at 3:40 PM Dan Shelton <[email protected]> wrote:
>
> Hello,
>
> some odd issue with ms-nfs41-client: when connecting to a FreeBSD
> 16.0-CURRENT main-n284403-895a97c875a0 (installed from
> FreeBSD-16.0-CURRENT-amd64-20260224-16822dac32ab-284159-disc1.iso) NFS server:
>
> Windows side:
> $ /sbin/nfs_mount -o rw 'F:' 'nfs://42.28.16.228//nfsdata'
> Successfully mounted '42.28.16.228@NFS@2049' to drive 'F:'
>
> ms-nfs41-client prints this warning:
> 204c: nfs41_superblock_getattr: Unexpected NFS error
> 'NFS4ERR_NOFILEHANDLE' while probing named attr support
> (the warning comes from
> https://github.com/kofemann/ms-nfs41-client/blob/master/daemon/nfs41_ops.c#L1394)
Hmm. The most obvious cause would be that the file system is not exported.
Check the /etc/exports and, if you use the ZFS nfshare property,
/etc/zfs/exports
and make sure the file system is exported?

As I've already mentioned, a packet capture is what I use to figure out
what is going on. On the FreeBSD server..
# tcpdump -s 0 -w out.pcap host <windows-client>
- For a simple failure like the above, start it before doing the mount
  and then kill it after the failure and send me "out.pcap".
  (If there is going to be stuff in out.pcap that you need to keep
   confidential, then you'll need to look at out.pcap yourself in wireshare.)

rick

>
> The Windows "FILE_NAMED_STREAMS" support is OFF then, which breaks our
> applications.
>
> Dan
> --
> Dan Shelton - Cluster Specialist Win/Lin/Bsd
>