From owner-freebsd-amd64@freebsd.org Sat Mar 19 02:06:40 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5658CAD5C2F for ; Sat, 19 Mar 2016 02:06:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2D8C8D32 for ; Sat, 19 Mar 2016 02:06:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2J26eYN053196 for ; Sat, 19 Mar 2016 02:06:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 208071] AutoFS seems to disturb NFS server Date: Sat, 19 Mar 2016 02:06:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: trasz@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 19 Mar 2016 02:12:51 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 02:06:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208071 Rick Macklem changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmacklem@FreeBSD.org --- Comment #5 from Rick Macklem --- Every time you mount(8) any file system on the NFS server, mountd reloads the /etc/exports. This has two effects: 1 - Unless you are running mountd with the "-S" option, the file systems will become unexported for a short period of time during the reload. 2 - If the new file system is mounted on top of the exported file system, mountd will try to export that new file system. --> NFS mounts can never be exported, so if the new file system is an NFS client mount, the export will no longer work. (This has been the case since 1985 and is in part the case because you can't safely put a file handle inside a file handle.) To fix #1, add "-S" to mountd_flags. #2 just won't work and needs to be avoided. You can look at /var/log/messages for entries related to export problems generated by mountd. I don't know amd-utils or autofs, but it may be that one of them uses mount(8) and the other does not. FreeBSD's mount(8) always sends a SIGHUP to mountd, which makes it reload /etc/exports. Basically #1 and #2 only occurs because mountd reloads /etc/exports and that happens when mountd receives a SIGHUP. It may be that amd-utils doesn't send a SIGHUP to mountd?) rick --=20 You are receiving this mail because: You are on the CC list for the bug.=