Date: Sun, 24 Dec 2023 16:01:02 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 275905] nfs client: mount becomes unresponsive Message-ID: <bug-275905-3630-6ETlTCWkCp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275905-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-275905-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=3D275905 --- Comment #5 from Lexi <lexi.freebsd@le-fay.org> --- the client keytab should be fine, since i only created it about 2 days ago = when i installed this host and there was no previous principal for this fqdn. 'kinit -k host/fqdn' on the client seems to work: # kinit -k host/ilythia.eden.le-fay.org # klist Credentials cache: FILE:/tmp/krb5cc_0 Principal: host/ilythia.eden.le-fay.org@EDEN.LE-FAY.ORG Issued Expires Principal Dec 24 15:54:16 2023 Dec 25 01:54:16 2023=20 krbtgt/EDEN.LE-FAY.ORG@EDEN.LE-FAY.ORG > Does this hang occur frequently or was this a "one time" hang on a mount = that usually behaves ok? as i mentioned, i only installed this host 2 days ago, so i can't say for s= ure, but so far it has reliably occurred twice about 10 hours after booting so it seems to be 100% reproducible. (iow, it never *hasn't* occurred at that ti= me.) in the mean time, i've temporarily switched the mount from sec=3Dkrb5p to sec=3Dkrb5 to see if this fixes the issue; aiui, this means no GSS should be involved after the initial mount, so i expect it will, but i'm happy to do = any other testing you need. --=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-275905-3630-6ETlTCWkCp>