Date: Mon, 19 Apr 2021 02:31:50 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255204] mountd: sometimes ignores SIGHUP with NFS 4 shares Message-ID: <bug-255204-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255204 Bug ID: 255204 Summary: mountd: sometimes ignores SIGHUP with NFS 4 shares Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: asomers@FreeBSD.org When it receives SIGHUP mountd is supposed to reload the exports list. But= in my experience, it sometimes does not. Sending additional SIGHUPs does not help, so I don't think it's due to a race. Restarting mountd is the only c= ure. Additional observations: * Observed on 12.2-RELEASE, so it's not related to bug 246597 * Observed with NFS 4.0 Linux clients. I think I've seen it with 4.1, too.= =20 I've never seen it with NFS 3. * The usual presentation is that I mount a client from a disallowed IP addr= ess, and the client gets EIO trying to access the share. Then I edit the source dataset's sharenfs property (which sends SIGHUP to mountd), but the client still gets EIO. I have to restart mountd to fix it. The next time this happens, I'll try to debug it in place. --=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-255204-227>