Page 1 of 1

NFS access fails with wrong not exported message

Posted: 28 May 2023, 02:09
by tommi2day
I created a NFS enabled shared folder. Wenn i try to access this shared folder it will deny as i could see in /var/log/messages (by the way: why i cant see this in the system logs in the gui?)
May 27 19:00:24 T9 rpc.mountd[17482]: refused mount request from pve2-st.local for /Volume1/vmdata1 (/): not exported
of cource, the share is exported, but this locks strange withe the quotes in front
grep /Volume1/vmdata1 /etc/exports
"/Volume1/vmdata1" 192.168.101.*(rw,async,crossmnt,insecure_locks,sec=sys,no_root_squash,anonuid=6,anongid=4)
"/Volume1/vmdata1" 192.168.110.*(rw,async,crossmnt,insecure,insecure_locks,sec=sys,no_root_squash,anonuid=6,anongid=4)
"/Volume1/vmdata1" 192.168.150.*(rw,async,crossmnt,insecure,insecure_locks,sec=sys,no_root_squash,anonuid=6,anongid=4)
the client host is in the allowed range
host pve2-st.local
pve2-st.local has address 192.168.110.42
Is this a bug in TOS5.1.34? I tried to update to TOS5.1.37, but this failed completly, see other thred.

I am now a little bit annoyed if such basic nas functions are not working prperly.

Thomas

Re: NFS access fails with wrong not exported message

Posted: 28 May 2023, 17:54
by TMlinda
{L_BUTTON_AT}tommi2day

Please check whether the NFS file service is enabled on the server, and check whether the shared folder to be mounted has NFS rules set. You can try to change the mapping method to "map all users as superusers".