SphericalRedundancy Posted November 6, 2020 Share Posted November 6, 2020 I currently have 8 NFS shares that are all working as expected configured as a private NFS share but I noticed today when I attempted to add a 9th NFS share that although the entry gets added to the /etc/exports file it does not actually export the new share as shown by showmount or exportfs -v. I noticed that when I run exportfs -ra to re-initilize the NFS service and have it export shares configured in /etc/exports it shows an error message about incorrect syntax for a bad option list. This points to line 9 in the /etc/exports file but line 9 is a completely different share that is currently working normally and exported successfully. If I remove line 9 by disabling that share in the Unraid GUI, the syntax error just moves up one line but I don't see any issues with the content of /etc/exports and I wouldn't expect any errors considering I haven't manually edited the file. All entries in /etc/exports were added by Unraid itself. I've attached some other images below for reference, the NFS share that is not working as expected is /mnt/user/tv. Unraid share settings in GUI: Content of /etc/exports: # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. "/mnt/user/backups" -async,no_subtree_check,fsid=102 192.168.1.10(sec=sys,rw,sync) "/mnt/user/comics" -async,no_subtree_check,fsid=108 192.168.1.38(sec=sys,ro,sync) 192.168.1.33(sec=sys,ro,sync) 192.168.1.17(sec=sys,rw,sync) "/mnt/user/downloads" -async,no_subtree_check,fsid=100 192.168.1.51(sec=sys,rw,sync) 192.168.1.52(sec=sys,rw,sync) 192.168.1.44(sec=sys,rw,sync) 192.168.1.27(sec=sys,rw,sync) 192.168.1.53(sec=sys,rw,sync) "/mnt/user/ebooks" -async,no_subtree_check,fsid=109 192.168.1.38(sec=sys,ro,sync) "/mnt/user/instructional" -async,no_subtree_check,fsid=110 192.168.1.38(sec=sys,ro,sync) "/mnt/user/movies" -async,no_subtree_check,fsid=107 192.168.1.47(sec=sys,ro,sync) "/mnt/user/other" -async,no_subtree_check,fsid=112 192.168.1.33(sec=sys,ro,sync) "/mnt/user/proxmox-isos" -async,no_subtree_check,fsid=105 192.168.1.14(sec=sys,rw,sync),192.168.1.15(sec=sys,rw,sync) "/mnt/user/tv" -async,no_subtree_check,fsid=106 192.168.1.47(sec=sys,ro,sync) Output of exportfs -v Any help with be very much appreciated as I don't understand what is happening. Thank you, Quote Link to comment
nikiforos Posted April 3, 2022 Share Posted April 3, 2022 Hi there, did you ever find a solution for this? I am having the same issue now. Thanks! Nick Quote Link to comment
SphericalRedundancy Posted April 3, 2022 Author Share Posted April 3, 2022 Unfortunately no I didn't, I kept having other issues as well so I migrated my files off of my unraid server and stopped using it. Quote Link to comment
nikiforos Posted April 4, 2022 Share Posted April 4, 2022 Thanks for your reply. I found a workaround which did the trick for me. I removed all the rules and set the NFS export to "No" on all my shares. I then deactivated and reactivated the NFS sharing in the Unraid settings. Afterwards, I enabled exporting one share at a time, always checking that "exportfs -ra" worked. Not entirely sure what the problem was, but everything's working now. Quote Link to comment
Holmesware Posted July 6, 2022 Share Posted July 6, 2022 The Whole Picture: On Server ZFS Data set = pool/data Mount Point = /pool/data 1. Make sure sharenfs=off (zfs set sharenfs=off pool/data) 2. edit /etc/exports, add line "/pool/data" -async,no_subtree_check,fsid=111 *(sec=sys,rw,no_root_squash,no_all_squash)" Note: fsid has to be a unique number for each share. Unraid starts them at 100 3. restart nfsd (/etc/rc.d/rc.nfsd restart) Make a script that inserts the line in step 2 into the /etx/exports file on boot. On Client Use the Unraid GUI on the Main tab to mount and NFS share Yes it connects My Issue: Permissions of files and folders on Client (all files 777 nobody:users) do not reflect those on the Server (770 <user name>:domain users> Is this something NFSv4 can solve? Making it an SMB share has the same issue with permissions. Both Client and Server connected to the same domain. Quote Link to comment
Recommended Posts
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.