Date: Thu, 14 Feb 2019 21:23:32 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 235582] rpc_svc_gss / nfsd kernel panic Message-ID: <bug-235582-3630-HTAUdXhnWX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235582-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-235582-3630@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=3D235582 --- Comment #21 from Peter Eriksson <peter.x.eriksson@liu.se> --- Just a quick feedback/comment: We've now been running our production servers with a patched kernel as per above since Monday night and so far everything seems to be running correctly... No kernel panics so far - *Fingers Crossed* :-) Just a quick wish for someone - would it be possible to have the CLIENT_MAX= and the hash table size increased a bit (like to 512/1024) in an "official" ker= nel patch for 11.2? 128/256 are very low numbers - especially since every client principal (HOST$@REALM) also uses up a slot in that table when a client connects...=20 So basically it just requires 64 clients (with a different user on each cli= ent) to run into the CLIENT_MAX limit (which I'm guessing will cause gssd extra = work so it's not a showstopper, just annoying :-). (There are a bit too many kernel-crashing problems reported with ZFS in 12.0 for us to upgrade there yet). I know I can build my own kernel with those limits increased but it would be nice to not have to do that (and distribute it to all our servers) whenever= a new kernel/security patch arrives... :-) /Lazy Bugger --=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-235582-3630-HTAUdXhnWX>