Date: Sat, 16 Jul 2022 14:19:10 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Peter <pmc@citylink.dinoex.sub.org>, "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: nfs stalls client: nfsrv_cache_session: no session Message-ID: <YQBPR0101MB97429BFA1F580F82F4E4A01DDD8A9@YQBPR0101MB9742.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <YtKpqjBITR/ocjiF@gate.intra.daemon.contact> References: <YtKpqjBITR/ocjiF@gate.intra.daemon.contact>
next in thread | previous in thread | raw e-mail | index | archive | help
--_002_YQBPR0101MB97429BFA1F580F82F4E4A01DDD8A9YQBPR0101MB9742_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Peter <pmc@citylink.dinoex.sub.org> wrote:=0A= > Hija,=0A= > I have a problem with NFSv4:=0A= > =0A= > The configuration:=0A= > Server Rel. 13.1-RC2=0A= > nfs_server_enable=3D"YES"=0A= > nfs_server_flags=3D"-u -t --minthreads 2 --maxthreads 20 -h ..."=0A= > mountd_enable=3D"YES"=0A= > mountd_flags=3D"-S -p 803 -h ..."=0A= > rpc_lockd_enable=3D"YES"=0A= > rpc_lockd_flags=3D"-h ..."=0A= > rpc_statd_enable=3D"YES"=0A= > rpc_statd_flags=3D"-h ..."=0A= > rpcbind_enable=3D"YES"=0A= > rpcbind_flags=3D"-h ..."=0A= > nfsv4_server_enable=3D"YES"=0A= > sysctl vfs.nfs.enable_uidtostring=3D1=0A= > sysctl vfs.nfsd.enable_stringtouid=3D1=0A= > =0A= > Client bhyve Rel. 13.1-RELEASE on the same system=0A= > nfs_client_enable=3D"YES"=0A= > nfs_access_cache=3D"600"=0A= > nfs_bufpackets=3D"32"=0A= > nfscbd_enable=3D"YES"=0A= > =0A= > Mount-options: nfsv4,readahead=3D1,rw,async=0A= > =0A= > =0A= > Access to the share suddenly stalled. Server reports this in messages,=0A= > every second:=0A= > nfsrv_cache_session: no session IPaddr=3D192.168...=0A= The attached little patch might help. It will soon be in stable/13, but is = not=0A= in releng/13.1.=0A= It fixes the only way I am aware of that the client's "nfscl" thread=0A= can get "stuck" on an old session and not do session recovery.=0A= It might be worth applying it to the client.=0A= =0A= This still doesn't explain how the session got broken in the first place.= =0A= =0A= rick=0A= =0A= Restarting nfsd and mountd didn't help, only now the client started to=0A= also report in messages, every second:=0A= nfs server 192.168...:/var/sysup/mnt/tmp.6.56160: is alive again=0A= =0A= Mounting the same share anew to a different place works fine.=0A= =0A= The network babble is this, every second:=0A= NFS request xid 1678997001 212 getattr fh 0,6/2=0A= NFS reply xid 1678997001 reply ok 52 getattr ERROR: unk 10052=0A= =0A= Forensics: I tried to build openoffice on that share, a couple of=0A= times. So there was a bit of traffic, and some things may have=0A= overflown.=0A= =0A= There seems to be no way to recover, only crashing the client.=0A= =0A= =0A= =0A= --_002_YQBPR0101MB97429BFA1F580F82F4E4A01DDD8A9YQBPR0101MB9742_ Content-Type: application/octet-stream; name="defunct-releng13.1.patch" Content-Description: defunct-releng13.1.patch Content-Disposition: attachment; filename="defunct-releng13.1.patch"; size=620; creation-date="Sat, 16 Jul 2022 14:19:06 GMT"; modification-date="Sat, 16 Jul 2022 14:19:06 GMT" Content-Transfer-Encoding: base64 LS0tIHN5cy9mcy9uZnNjbGllbnQvbmZzX2NscnBjb3BzLmMub3JpZwkyMDIyLTA3LTE2IDA3OjA0 OjI2LjUxNzM2NTAwMCAtMDcwMAorKysgc3lzL2ZzL25mc2NsaWVudC9uZnNfY2xycGNvcHMuYwky MDIyLTA3LTE2IDA3OjA0OjI2LjUxNjU3NTAwMCAtMDcwMApAQCAtMTA2MCw4ICsxMDYwLDE0IEBA IG5mc3JwY19zZXRjbGllbnQoc3RydWN0IG5mc21vdW50ICpubXAsIHN0cnVjdCBuZnNjbGNsaQog CQkJICogaW4tcHJvZ3Jlc3MgUlBDcy4KIAkJCSAqLwogCQkJdHNlcCA9IE5VTEw7Ci0JCQlpZiAo VEFJTFFfRklSU1QoJm5tcC0+bm1fc2VzcykgIT0gTlVMTCkKKwkJCWlmIChUQUlMUV9GSVJTVCgm bm1wLT5ubV9zZXNzKSAhPSBOVUxMKSB7CisJCQkJLyoKKwkJCQkgKiBNYXJrIHRoZSBvbGQgc2Vz c2lvbiBkZWZ1bmN0LiAgTmVlZGVkCisJCQkJICogd2hlbiBjYWxsZWQgZnJvbSBuZnNjbF9oYXNl eHBpcmVkKCkuCisJCQkJICovCiAJCQkJdHNlcCA9IE5GU01OVF9NRFNTRVNTSU9OKG5tcCk7CisJ CQkJdHNlcC0+bmZzZXNzX2RlZnVuY3QgPSAxOworCQkJfQogCQkJVEFJTFFfSU5TRVJUX0hFQUQo Jm5tcC0+bm1fc2VzcywgZHNwLAogCQkJICAgIG5mc2NsZHNfbGlzdCk7CiAJCQkvKgo= --_002_YQBPR0101MB97429BFA1F580F82F4E4A01DDD8A9YQBPR0101MB9742_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQBPR0101MB97429BFA1F580F82F4E4A01DDD8A9>