From owner-freebsd-current@FreeBSD.ORG Thu Apr 23 09:16:59 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 277A1891 for ; Thu, 23 Apr 2015 09:16:59 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B01BE112B for ; Thu, 23 Apr 2015 09:16:58 +0000 (UTC) Received: by wiax7 with SMTP id x7so7989974wia.0 for ; Thu, 23 Apr 2015 02:16:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=9d9BasXJqrwlBpg1YUdfO6cKfvNyEl0/ohjoIpENuXc=; b=ktQnsuBSy1XIPLR+s5a+pnYtTkUyQyx/TKN65u+Ic60ZK+KtZ2Bd9VvR9TcSq9nSvw 6G8ABiT2Oejh+Cu0tg7DNSoyMb8pwUokx0Jju/slmasbO9fIyzO0L52RgPAJb/2HNu6o 3dSQl89jwEDw/L4sbIeHsKYfVCKbbiOSL4cJkIHj07a093vMROFrayX+xtpyncpoisGD uBu6BgrQhwZAbeT8M0OV2Exi2hZexwHXp4y+Y9IwFbIkV/0p402PV7NlJOYMd0CGirAX nqTYkQMpQ30/rcR0aftLhBV2/A/3zCj+83l2mffL4aqaSLarFFtreA2HTnukLA9bAAbU WkJQ== X-Received: by 10.194.19.197 with SMTP id h5mr3423442wje.109.1429780616893; Thu, 23 Apr 2015 02:16:56 -0700 (PDT) Received: from brick.home (dgp65.neoplus.adsl.tpnet.pl. [83.23.171.65]) by mx.google.com with ESMTPSA id dg8sm11159584wjc.9.2015.04.23.02.16.55 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Apr 2015 02:16:55 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Thu, 23 Apr 2015 11:16:53 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: David Boyd Cc: freebsd-current@freebsd.org Subject: Re: AUTOFS and NFS not playing together nicely Message-ID: <20150423091653.GA1607@brick.home> Mail-Followup-To: David Boyd , freebsd-current@freebsd.org References: <1429477202.29812.38.camel@gemini.bsd1.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1429477202.29812.38.camel@gemini.bsd1.net> User-Agent: Mutt/1.5.23 (2014-03-12) 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: Thu, 23 Apr 2015 09:16:59 -0000 On 0419T1700, David Boyd wrote: > 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. That's an interesting bug. I can reproduce it, but hadn't tracked down the cause just yet. I'll work on that shortly. Thanks for reporting!