December 18, 20223 yr Because of a large library of Steam games that are installed on the Unraid server at home and the problems between NFSv3 not supporting UTF-8 and the UTF-16 translation that the Windows NFS Client (to my understanding) does, there are Asian character in map names that prevents the maps to be accessed (read) by the Windows client, so Steam fails to run them directly from the NFS Shares. I have been applying what is said in the forum below, but users there are mentioning a Linux client. No matter if I change the /etc/nfsmount.conf (changing "Defaultvers=" to 4) and /etc/exports (adding "V4:" in fromt of every line) files and making them survive reboots by copying them over from the Flashdrive before the emhttp line, "nfsstats -s" still answers with NFS v3 statistics. None for v4. I would like to know if Unraid is indeed running NFSv4+ (V4 was mentioned in the 6.10 release notes), do I need to add the lines after the "emhttp" line or how to force it to use V4 and if the Windows 10 Pro even supports NFSv4+, because if the latter is the case I'll have to find support somewhere else. Update: Seems Windows NFS clients only support NFS up to v3. I might have to build my own Windows NFS 4.1 Client. I have never done this. Got some instructions from https://github.com/kofemann/ms-nfs41-client (9 years old? Oh boy...). Now to build it with MS Visual Studio 2022 SDK and WDK or whatever it's called... Or drop NFS for SMB/CIFS... Edited December 18, 20223 yr by Ymetro minor title correction and update for scouring the internet about this topic + minor corrections
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.