I am really curious: why on earth is it possible to connect to unRAID with a macOS client using the NFS protocol and it works flawless whereas on every other NFS server (debian stretch, slackware) the connection immediately almost comes to a halt?

 

when connecting to an NFS server using der Finder.app (keyboard shortcut CMD-K nfs://server/export) to anything other than unRAID the mounted share is almost unusable. I can nonnect to NFS exports running on debian or slackware using the terminal command "mount" with the option "locallocks" and it works just fine. I even copied the /etc/exports file from unRAID to a freshly installed debian or slackware server and it's still not possible to get a usable connection when mounting with CMD-K in the Finder.app.

 

are there any other options for the NFS server I can tweak besides  /etc/exports ?

I'm not sure I understand. Are you saying Unraid is working fine for you but you are having difficulties with another linux?

yep, that's exactly the case. I'm just curious about what unRAID is doing different with the NFS shares. I spent hours while trying to find out why this is the case. unfortunately I'm stuck now... there's must be something I have overlooked.

 

mounting the NFS share from the terminal works fine as long as I'm using the "locallocks" option. works fine with unRAID and debian or slackware.

 

when mounting the NFS share using the Finder.app (CMD-K nfs://server/export) it's only usable if I use unRAID as server. with debian or slackware the connection is somehow broken: it takes ages to list a directory or to transfer files. it's not just slower. eg: it takes several minutes to list a directory.