Date: Wed, 25 Nov 2020 06:42:17 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 251347] NFS hangs on client side when mounted from outside in Jail Tree (BROKEN NFS SERVER OR MIDDLEWARE) Message-ID: <bug-251347-227-Ja5pChOy4g@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251347-227@https.bugs.freebsd.org/bugzilla/> References: <bug-251347-227@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=3D251347 --- Comment #3 from Arne Steinkamm <arne@Steinkamm.COM> --- Ah few new findings: binding portmapper, nfsd, mountd, et.al. to one ip address on server and cl= ient changed nothing. This is no surprise, I'm in the try&error phase. Switching to NFSv4 makes no difference but gives a more detailed error mess= age on the console every time I stop the jail associated with the nullfs mount. newnfs: server '192.168.67.38' error: fileid changed. fsid deaf3afe:f75a86d= e: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR MODDLEWARE) This message is only on the console. There is nothing in dmesg output or log files. Can someone enlighten me how to decode the error message? I got the exact s= ame numbers twice now so I'm curious. Thanks in advance, .//. Arne --=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-251347-227-Ja5pChOy4g>