[Bug 260011] Unresponsive NFS mount on AWS EFS
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 260011] Unresponsive NFS mount on AWS EFS"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 25 Nov 2021 17:13:59 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260011 --- Comment #6 from Rick Macklem <rmacklem@FreeBSD.org> --- Oh, and my comment 2.r.t. don't run the nfscbd may not be good advice. Here's a more complete answer: The nfscbd(8) provides callback handling when it is running. Callbacks need to be working for the server to issue delegations or layouts (the latter is pNFS only). When the nfscbd(8) is not running, the server should work fine and never issue delegations or layouts. It should set a flag in the reply to the Sequence operation (the first one in each compound RPC) called SEQ4_STATUS_CB_PATH_DOWN. This is an FYI for the client. I found another round of bugs related to delegations during a recent IETF NFSv4 testing event. These are fixed in stable/13, but not 13.0. --> As such, delegations are problematic and you don't want them being issued. --> Don't run the nfscbd(8) daemon. Unfortunately Amazon does not attend these testing events, so what their server does is ??? for me. However, if it is known that the Amazon EFS never issues delegations or layouts (I believe cpercival@ said that was the case three years ago), then the server might be broken and get "perterbed" by the callbacks not working. --> In this case, you should run the nfscbd daemon by setting nfscbd_enable="YES" in your /etc/rc.conf or start it manually. And, given the above, I think you can see why my initial advice was just "don't run it". -- You are receiving this mail because: You are the assignee for the bug.