Skip to content
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

Closed
twoholes opened this issue Sep 14, 2021 · 8 comments
Closed

mount error #45

twoholes opened this issue Sep 14, 2021 · 8 comments

Comments

@twoholes
Copy link

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...

@twoholes
Copy link
Author

I have printed the debug info , the func onGetAttr():
fs, path, err := userHandle.FromHandle(handle)
if err != nil {
return &NFSStatusError{NFSStatusStale, err} // this error happened
}

@twoholes
Copy link
Author

图片

@willscott
Copy link
Owner

The screenshot is showing the client attempting to talk NFS v4 rather than v3.

You may need something like -t nfs3 rather than nfsvers=3 on your platform

@twoholes
Copy link
Author

The screenshot is showing the client attempting to talk NFS v4 rather than v3.

You may need something like -t nfs3 rather than nfsvers=3 on your platform
hi,
Thank you for your answer, thank you.
Another question is:
mount use nfsv3, the client mount print like this:


mount.nfs: access denied by server while mounting 10.243.88.235:/public

the dir access is OK, I have set nobody:nobody.

the following is net dump:
图片

@willscott
Copy link
Owner

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.

@twoholes
Copy link
Author

sending

In the same server, I start NFS(default 2049) and rpcbind,then in the client I mount like this:

mount -t nfs -onfsvers=3,tcp,noacl 10.243.88.235:/public /share/

it returns OK.
But when I start nfs server with osview command, it happens "access denied by server " problem.

tcpdump NFS(2049):
图片

I am perplexed with the result from osview ..
I do just like the useage:
图片

@twoholes
Copy link
Author

Hi, willscott :
I try the deamon(osview) in centos7, it's OK.
also thank you for helping me.
maby client mount has some problem in rel6 ..

thank you

@willscott
Copy link
Owner

Perhaps you have a different option you need for the client in that version.
In the latest screenshot, you'll see that the 'NFSACL' protocol is used. That may mean you need a different option other than 'noacl' to disable that part of NFS from that client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants