-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mount error #45
Comments
I have printed the debug info , the func onGetAttr(): |
The screenshot is showing the client attempting to talk NFS v4 rather than v3. You may need something like |
mount.nfs: access denied by server while mounting 10.243.88.235:/publicthe dir access is OK, I have set nobody:nobody. |
The response in the screenshot you highlight appears to be successful. The screenshot only shows packets for the 'Mount' protocol, not for the 'NFSv3' protocol. Is it possible that your client is not properly sending its NFSv3 requests also to the server? If it is trying to use a portmapper service, rather than sending messages to the server directly, it won't locate the port automatically. |
Hi, willscott : thank you |
Perhaps you have a different option you need for the client in that version. |
hi:
1 start example osview like this:
./osview /public 2045
2 use mount like this:
mount -t nfs -o port=2045,mountport=2045,nfsvers=3,tcp -o nolock 10.243.88.235:/public/ /share/
3 the output at server console:
2021/09/14 20:11:49 request: RPC #4228535329 (nfs.Null)
2021/09/14 20:11:49 request: RPC #4245312545 (nfs.GetAttr)
2021/09/14 20:11:49 call to 0x5dc6a0 failed: Invalid file handle
How can I do above the problem...
help me~~~ thank you
My English is terrible, please forgive me...
The text was updated successfully, but these errors were encountered: