Date: Sun, 28 Aug 2022 19:20:35 +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: <YT2PR01MB9729CC92661B72C491C115F1DD779@YT2PR01MB9729.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
Also, if you have multiple clients, make sure that they
all have unique /etc/hostid's. A duplicate machine with
the same /etc/hostid as another one will screw up NFSv4
really badly.
rick
________________________________________
From: owner-freebsd-stable@freebsd.org <owner-freebsd-stable@freebsd.org> o=
n behalf of Peter <pmc@citylink.dinoex.sub.org>
Sent: Saturday, July 16, 2022 8:06 AM
To: freebsd-stable@freebsd.org
Subject: nfs stalls client: nfsrv_cache_session: no session
CAUTION: This email originated from outside of the University of Guelph. Do=
not click links or open attachments unless you recognize the sender and kn=
ow the content is safe. If in doubt, forward suspicious emails to IThelp@uo=
guelph.ca
Hija,
I have a problem with NFSv4:
The configuration:
Server Rel. 13.1-RC2
nfs_server_enable=3D"YES"
nfs_server_flags=3D"-u -t --minthreads 2 --maxthreads 20 -h ..."
mountd_enable=3D"YES"
mountd_flags=3D"-S -p 803 -h ..."
rpc_lockd_enable=3D"YES"
rpc_lockd_flags=3D"-h ..."
rpc_statd_enable=3D"YES"
rpc_statd_flags=3D"-h ..."
rpcbind_enable=3D"YES"
rpcbind_flags=3D"-h ..."
nfsv4_server_enable=3D"YES"
sysctl vfs.nfs.enable_uidtostring=3D1
sysctl vfs.nfsd.enable_stringtouid=3D1
Client bhyve Rel. 13.1-RELEASE on the same system
nfs_client_enable=3D"YES"
nfs_access_cache=3D"600"
nfs_bufpackets=3D"32"
nfscbd_enable=3D"YES"
Mount-options: nfsv4,readahead=3D1,rw,async
Access to the share suddenly stalled. Server reports this in messages,
every second:
nfsrv_cache_session: no session IPaddr=3D192.168...
Restarting nfsd and mountd didn't help, only now the client started to
also report in messages, every second:
nfs server 192.168...:/var/sysup/mnt/tmp.6.56160: is alive again
Mounting the same share anew to a different place works fine.
The network babble is this, every second:
NFS request xid 1678997001 212 getattr fh 0,6/2
NFS reply xid 1678997001 reply ok 52 getattr ERROR: unk 10052
Forensics: I tried to build openoffice on that share, a couple of
times. So there was a bit of traffic, and some things may have
overflown.
There seems to be no way to recover, only crashing the client.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YT2PR01MB9729CC92661B72C491C115F1DD779>