From owner-freebsd-amd64@freebsd.org Wed Mar 16 19:42:05 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 0E285AD266F for ; Wed, 16 Mar 2016 19:42:05 +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 D9AE1C2E for ; Wed, 16 Mar 2016 19:42:04 +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 u2GJg4uW052566 for ; Wed, 16 Mar 2016 19:42:04 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: Wed, 16 Mar 2016 19:42:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: dlt_cjo@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: 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: Wed, 16 Mar 2016 20:19:28 +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: Wed, 16 Mar 2016 19:42:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208071 Bug ID: 208071 Summary: AutoFS seems to disturb NFS server Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: dlt_cjo@yahoo.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org I'm currently working to move my organization from am-utils to autofs and h= ave run into a snag. I've got three non-prod FreeBSD 10.2-RELEASE-p13 (as repo= rted by freebsd-version) machines that export NFS. If I'm transferring data fro= m a client and attempt an autofs mount elsewhere on the server, the mount betwe= en the client and server seems to be disturbed in a way that I haven't been ab= le to define, as there's no in-your-face error. To recreate: * Export a file system on the NFS server(nfs3). * NFS mount the server from a client(nfs3). * Run an automatic iozone benchmark from the client on the NFS mount. (iozo= ne -a) * ssh into the server, change directory into an autofs namespace, then do a directory listing to cajole it into mounting a file system on yet another N= FS machine(nfs3). * The NFS client running the iozone should now error out with a "Can not op= en temporary file iozone.tmp for read, open: Permission denied" or "fsync: Input/output error" I can't quite place my finger on it. It seems as if the act of mounting another filesystem with AutoFS is disturbing the NFS server in some way.=20= =20 This doesn't happen when using a similarly configured am-utils as the automounter & I'm able to duplicate on all three FreeBSD machines. Running automountd in debug mode doesn't seem to report any errors that would lead = me to believe it's a configuration issue. (Though I'm certainly open to that b= eing a problem!) --=20 You are receiving this mail because: You are on the CC list for the bug.=