Are there any errors in the Ganesha log? Also, what is the client side mount command? And just to make sure, they aren't trying to mount from the same host running Ganesha?
To verify you can run cthon04 lock tests over an NFSv3 mount to the server. Check the sockets before and after with this: netstat -eap | grep `pidof ganesha.nfsd` Crosscheck with looking at the open files before and after: ls -l /proc/`pidof ganesha.nfsd`/fd You can correlate the sockets with the fds We expect to not see than a few udp sockets (rquotad if that is running, nfs, and maybe 2 others). With the bug not fixed, the cthon04 lock tests should result in a bunch of open sockets that may be labeled as statd.
I should have been not so lazy... To run the lock tests: [root@dhcp35-93 cthon04]# ./server -lf -o vers=3 -p /arbiter-vol -m /arbiter-vol -N 1 dhcp35-100.lab.eng.blr.redhat.com
It would also be good to verify the socket output before/after cthon04 without the fix.
The without fix definitely shows ports not closed after cthon04 run while with fix it shows the ports closed after the cthon04 run. So looks good.
Looks good.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (nfs-ganesha bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:1459