From owner-freebsd-current@FreeBSD.ORG Sun Apr 19 21:00:17 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2BB4AA7C for ; Sun, 19 Apr 2015 21:00:17 +0000 (UTC) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id F0B4BD2E for ; Sun, 19 Apr 2015 21:00:16 +0000 (UTC) Received: from [96.28.24.204] ([96.28.24.204:28658] helo=[192.168.209.109]) by dnvrco-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 8A/F6-10851-85714355; Sun, 19 Apr 2015 21:00:08 +0000 Message-ID: <1429477202.29812.38.camel@gemini.bsd1.net> Subject: AUTOFS and NFS not playing together nicely From: David Boyd To: freebsd-current@freebsd.org Date: Sun, 19 Apr 2015 17:00:02 -0400 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.5 (3.8.5-31.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.64.130:25 X-Authority-Analysis: v=2.1 cv=GKuGE49K c=1 sm=1 tr=0 a=LAeh8JulWguKKqZdjpwXog==:117 a=LAeh8JulWguKKqZdjpwXog==:17 a=ayC55rCoAAAA:8 a=IkcTkHD0fZMA:10 a=UNWf5WQ7AAAA:8 a=mjlnPRs6AAAA:8 a=xiTNktAfJqfuuXK_zOQA:9 a=QEXdDO2ut3YA:10 X-Cloudmark-Score: 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2015 21:00:17 -0000 At the risk of being dubbed insane, here goes: On five FreeBSD 10.1-RELEASE-p9 production servers autofs(5) is enabled and working as advertised. On the same servers nfs v3 clients are also fat, dumb and happy. On a test server where autofs(5) is also enabled and working well, I am testing nfs v3 (later v4) server. Strange things are happening. When nfs mountd(8) is running, the autofs(5) auto-mount (via automountd) function seems to work, but the autofs(5) auto-unmount (via autounmountd) never occurs. Without nfs mountd(8), when the filesystem /disc is auto-mounted (via autoumountd), the mount(8) command shows status of (ufs, local, journaled soft-updates, auto-mounted) for the auto-mounted filesystem and after the autofs(5) timeout period (600 seconds) the filesystem is auto-unmounted (via autounmountd). No problem. With nfs mountd(8) the mount(8) command shows (ufs, local, journaled soft-updates). The auto-mounted filesystem is never (a long, long time) unmounted. Big problem. Without nfs mountd(8) running, the mount(8) command "mount -o automounted /dev/ada0p8 /disc" mounts the filesystem and the mount(8) command shows (ufs, local, journaled soft-updates, automounted) for the manually mounted filesystem and after the autofs(5) timeout period (600 seconds) the filesystem is auto-unmounted even though it was not mounted automatically. No problem. With nfs mountd(8), the mount(8) command "mount -o automounted /dev/ada0p8 /disc" mounts the filesystem but the mount(8) command shows (ufs, local, journaled soft-updates) and after the timeout period (600 seconds) the filesystem is remains mounted. Big problem. It appears that nfs mountd(8) is interferring with the mount(8) command's -o option processing but admittedly that is just a very weak SWAG. I have adequate hardware (real and virtual) to do any testing that may be suggested. Most days there is no time constraint either. -------------------------------------------------------- The /etc/auto_master file is two lines: 1:/net -hosts -nobrowse,nosuid (original) 2:/- /etc/autofs/auto_disc -------------------------------------------------------- The /etc/autofs/auto_disc file is one line: 1:/disc -fstype=ufs :/dev/ada0p8 -------------------------------------------------------- Once again, everything works well when nfs mountd(8) is not present in the system. Thanks for any assistance that you may be able to supply. David Boyd.