Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Mar 2016 19:42:04 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 208071] AutoFS seems to disturb NFS server
Message-ID:  <bug-208071-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
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 the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208071-8>