-
Notifications
You must be signed in to change notification settings - Fork 33
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
NFSv3 mount hangs in 3510.2.1 NFSv4.1 works fine #1444
Comments
Could someone look into this? |
bump |
@kthommandra hello, I can't reproduce the issue via a Kubernetes deployment. I tried with two different kernel versions:
Did you try with newer Flatcar versions? |
Hello @kthommandra, In addition to @tormath1, I have also tried to reproduce the behaviour using:
There were no hangs in my testing. @kthommandra, Can you please elaborate on how did you install the NFS server or what NFS hardware box are you using? Thanks. |
I have not tried newer flatcar versions yet. Will do. |
We are using an NFS appliance and not Linux NFS server. |
Description
sudo mount -t nfs -overs=3 NFSSERVER:/SHARE /tmp/mountdir
The above command hangs. Upon dumping the /proc/PID/stack I see the following
[<0>] lockd_up+0x1f/0x2b0 [lockd]
[<0>] nlmclnt_init+0x28/0xc0 [lockd]
[<0>] nfs_start_lockd+0xdd/0x120 [nfs]
[<0>] nfs_init_server.isra.0+0x1f3/0x350 [nfs]
[<0>] nfs_create_server+0x7f/0x220 [nfs]
[<0>] nfs3_create_server+0xc/0x60 [nfsv3]
[<0>] nfs_try_get_tree+0x12c/0x210 [nfs]
[<0>] vfs_get_tree+0x22/0xc0
[<0>] path_mount+0x469/0xa40
[<0>] __x64_sys_mount+0x107/0x140
[<0>] do_syscall_64+0x38/0x90
[<0>] entry_SYSCALL_64_after_hwframe+0x61/0xcb
rpc-statd.service is running on the node
If I re-run the above command with -o nolock then the mount succeeds.
If I use NFSv4 (different NFS server and share) then the mount succeeds.
I tested the same NFSv3 mount on one of the older nodes in our cluster 2983.2.1 and v3 mount works fine.
Impact
This bug is preventing mount of NFSv3 shares. For one of our NFS share we have requirement to use V3 only.
Environment and steps to reproduce
The command stalls and is Ctl-Cable
Expected behavior
mount using NFSv3 should succeed
Additional information
The text was updated successfully, but these errors were encountered: