NFS3 clients go through portmapper to access nfsd.
Up to unraid 6.12.10 nfsd and lockd were registered with portmapper, so nfs3 clients worked.
Starting with 6.12.11 nfsd and lockmanager are not registered with portmapper, so nfs3 clients fail to mount shares from unraid nfsd.
NFS4 clients to not go through portmapper to access nfsd, this is why nfs4 clients still work with 6.12.11.
To be correct: after rebooting unraid 6.12.11 all necessary rpc daemons are registered with portmapper as longas the array has not been started. After starting the array, nfsd and lockmgr are gone from portmapper (see rpcinfo on the console).
Also, with KODI using NFS 4 seems to be no universal solution. It works for video files but it doesn't work for many music files (NFS4: READ (path (null)) failed with NFS4ERR_OLD_STATEID(-5), NFS4: CLOSE (path (null)) failed with NFS4ERR_BAD_STATEID(-22)). This does NOT seem to be a result from lockmgr missing from portmapper, as when using NFS3 with Kodi and unraid 6.12.10 this just works fine. I would gues sit is an implementation problem in the Kodi NFS4 client.
Bottom line: I had to downgrade from 6.12.11 to 6.12.10 to be able to use Kodi using NFS3 and unraid. It is one main use case for me. (I do not want to switch to SMB)
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.