Date: Sun, 01 Nov 2020 22:00:27 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 250770] AWS EC2 system freezes up possibly associated with NFS (EFS) Message-ID: <bug-250770-27103-iEgYQR2ChF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250770-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-250770-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250770 --- Comment #7 from Rick Macklem <rmacklem@FreeBSD.org> --- In your initial post you show: nfsv4,minorversion=3D1,oneopenown so why was it hanging then? However, you are correct that oneopenown is needed for EFS and it only applies to minorversion 1 (or higher for FreeBSD13 if EFS supports it). I suppose I thought that NFSv4.1 was obvious shorthand for NFS version 4 minorversion 1, but the man page can be updated to clarify that. Btw, if you do "nfsstat -m" on the client, you see what mount options are actually being used. (The rsize, wsize is capped at vfs.maxbcachebuf, which is 64K by default and can be increased to MAXPHYS.) Oh, and I find the best way to debug these things is looking at a packet capture in wireshark. You can do the capture via "tcpdump -s 0 -w out.pcap host <server>" on the client and then load out.pcap into wireshark. (Unlike tcpdump, wireshark knows NFS.) Anyhow, sounds like you have it working now, rick --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250770-27103-iEgYQR2ChF>