https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260146
--- Comment #3 from Rick Macklem <[email protected]> --- Hmm, looks like you are using NFSv3. If you are running rpc.lockd, it is a fundamentally broken protocol (NLM). - If this is the case, try either the "nolockd" mount option or "nfsv4,minorversion=1" for your mount. If this doesn't resolve the problem, please provide the output for all of the following when the hang has occurred. nfsstat -m ps axHl procstat -kk netstat -a nfsstat -E -c <-- done at least twice about a minute apart Also, since you know how to reproduce the problem, you can capture packets while it happens. Before the hang run: tcpdump -s 0 -w out.pcap host <nfs-server> --> Then reproduce the problem and kill the tcpdump 1 minute after the hang has occurred. Put out.pcap here as an attachment. (Btw, if you want to look at out.pcap, use wireshark. tcpdump knows almost nothing about NFS packets, whereas wireshark can decode them nicely.) I have not heard of a FreeBSD client hang problem. There is a known TCP layer issue, but it causes hangs when the server is running 13.0 and I do not think the problem occurs when the server is 12.3. I have heard of issues when using vnet jails, but I doubt you are doing that. Also, hangs are often network fabric related. Disabling TSO on both client and server often helps. Of using a different network driver/chip if that is feasible (for example, for re devices the driver in ports sometimes works better than what is in the system, depending on which re chip you have.) -- You are receiving this mail because: You are the assignee for the bug.
