gcolds

Sorry for taking so long to respond. I just noticed you're post. I have not had a single Stale File handle error on my system since I disabled hard links. It has made me have to find an alternative backup solution for my linux desktop (I moved from BackInTime to Borg with Vorta) but nothing else has been a problem since. -Greg

Just wanted to finish this out with a bit of performance bench marking that I promised to last weekend. I've attached a markdown file to this post with my testing details since I didn't want to make this post too long. This testing has been an odyssey for me as I understand now that I've had my NSF mounts configured in ways that caused me some strange issues that I didn't know were related to my mount settings. I also learned that using systemd for mounts lets me recover from stale file handle errors much more easily. I'll just summarize by saying performance is not improved on a 10G network consistently when using v4 though things seem to be much more robust with v4. I still have to experiment with mount options and NFS server options, but I think I'm done for now unless I get a specific request. -Greg NFSv4 Testing.md

I have not seen this problem on my system with 6.9.2 and up but strictly speaking this thread is about NFSv4 support. You might want to post elsewhere about the standby issue or see if there is a bug report open on it already. -Greg

What is the drive standby issue? -Greg

I did have to to manually remount all my nfs shares to get them to work again. Understood, just wanted to put the thought out there. Honestly I'm just over the moon at having v4 support and can easily live with the current situation. -Greg

Ok, over the weekend I've been messing around with the v4 support and wanted to report that no matter what I did I found my NFSv4 mounts to be as rock solid reliable as my Synology and QNAP boxes were (Unraid replaced those boxes but I still keep them around as examples of well optimized SMB and NFS configs). My Steam game library is mostly stored on my Unraid box and that was hit or miss in terms of if a given game would launch or not. That has changed and every game that launches locally on my system also launches when run from the nfsv4 share. I make the distinction because most of my games are Windows games being run with Valve's Proton compatibility layer and Proton is flaky when run over NFS3, don't know why. I have not had any of this flakiness at all. Everything launches except games that are generally not compatible with Proton for some reason (DRM, Anticheat, etc). Stale file handle errors only occurred 1 time this whole weekend. With hard links on, I did all the things I recall would reliably cause the issue and the only time it occurred was when I stopped and then restarted the Array without remounting my NFS shares on my desktop and then doing an ls in one of the share directories. I'm not ready to declare stale file handles a non-issue after only one weekend of testing but it certainly seems to be an improvement. Since My Unraid box has an AMD Threaddripper 2990wx and my primary desktop has an AMD Threadripper 3097x (both with 64 GB of RAM) and I'm running a 10G network at home (just because I can, not because I need it), performance was always very good (if not always reliable). I did not notice an improvement since I always had rather fast speeds. I got more wrapped up in testing all the scenarios that would cause reliability issues (including data corruption or loss) this weekend. I hope to do some NFSv3 vs NFSv4 bench-marking next weekend @limetech reported not being able to get another Unraid box to mount in v4 mode. I can confirm this. I used the following command to manually mount a share from my Synology box: mount -t nfs4 -o proto=tcp,port=2049 10.0.1.10/volume1/stuff /mnt/remotes/10.0.1.10_stuff This give me the following error: mount.nfs4: No such device After some investigation of my Synology, QNAP, and Manjaro Linux boxes, I think the problem is a missing kernel module (nfsv4.ko.zx). So if that gets added, I'll try mounting again. Misc thought: It would be nice if the Unraid GUI exposed the ability to configure the NFS server to the extent you can configure Samba. It could be nice to be able to put custom parameters in nfs.conf as you can with the smb.conf without going through the terminal. Thanks again @limetech -Greg

Ok, I just figured out that if you are using systemd to mount on your desktop, you should not change the Type from nfs to nfs4. That caused my mounts to stop mounting after I rebooted unraid. -Greg

It works! As requested, I posted about my experience getting NFS4 working here. Thanks so much for this limetech -Greg

I'll get right on this. The client I'm using nfs-utils from the Manjaro Linux Repo. Nothing special I think.

I'll be happy to test out in rc2. I exclusively only use NFS for my mounts since Steam games don't launch from SMB mounts on linux consistently).

I am new to unraid and would also like to add my voice to this request. I previously made a file store and media server with Ubuntu Server and went through much pain with NFS3 that I ultimately got resolved by switching to NFS 4. I use Ubuntu as my primary desktop and was unable to get backups using programs that use hardlinks working until the switch (I use a program called BackInTime). My steam library is on my file server (as in I run games, including windows games via proton, from my server over nfs) and this was extremely unreliable until I started using NFS4. Now that I'm on unraid, I'm dealing with all those old problems that I haven't had in the 4 years I was running Ubuntu with mergerFS. I don't regret the move as unraid lets me expand the things I can do with my server with way more ease but the loss of NFS 4 has been painful. Please enable NFS4 support.