From owner-freebsd-current@FreeBSD.ORG Mon Aug 4 17:41:52 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92511FA9; Mon, 4 Aug 2014 17:41:52 +0000 (UTC) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3FED21D8; Mon, 4 Aug 2014 17:41:51 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id w61so8131272wes.39 for ; Mon, 04 Aug 2014 10:41:50 -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 :content-transfer-encoding:in-reply-to:user-agent; bh=pg1Olvv6j8jiXU1Q8+gDz7CFz6pdXrEZ1KXGPJFM8Eo=; b=GGoG3xdXleAFhznhMPYSNHWQKv6w3FLDwfa5Nwl4ViaF47xAHJbg/EZ0sgbxjC5osg uJq0HDmwL9oXSX44WzsbsSZ3Ui9KVF7JgF2uNKR4WhrG+4N+sSRuQPEL+dKbp2egE+Uy zhD44WsmEwYvdK6SaH/0t+HiHbl1SJ7hsKmigUiYflwLAweTiWoTRqc1Xj6hEFqXFP2G svSIUD0XGmjoiVzhcVQTBOzts/JOsra7hWt45aedl1zcDvTJ49rm3zBwrDzFdBpxNbFU 6KN+011ax51shlJc9xCvXB1HwdcEKr01W+wdnM0p/RgMqbtxBkdGMYcwAhgCtyqDw5vJ 0E2A== X-Received: by 10.180.39.172 with SMTP id q12mr31003625wik.55.1407174109991; Mon, 04 Aug 2014 10:41:49 -0700 (PDT) Received: from pc5.home (adhg143.neoplus.adsl.tpnet.pl. [79.184.162.143]) by mx.google.com with ESMTPSA id 10sm45007077wjx.26.2014.08.04.10.41.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Aug 2014 10:41:49 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Mon, 4 Aug 2014 19:41:53 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: "Bjoern A. Zeeb" Subject: Re: [CFT] Autofs. Message-ID: <20140804174153.GA33041@pc5.home> Mail-Followup-To: "Bjoern A. Zeeb" , freebsd-current@FreeBSD.org, freebsd-arch@FreeBSD.org References: <20140730071933.GA20122@pc5.home> <3DA39B51-4CE5-437B-9B03-7E34CC954A7E@lists.zabbadoz.net> <20140804161710.GA32801@pc5.home> <5C88BFBD-798C-4F99-92E2-5F75FE622613@lists.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5C88BFBD-798C-4F99-92E2-5F75FE622613@lists.zabbadoz.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org, freebsd-arch@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 04 Aug 2014 17:41:52 -0000 On 0804T1635, Bjoern A. Zeeb wrote: > > On 04 Aug 2014, at 16:17 , Edward Tomasz Napierała wrote: > > > On 0804T1252, Bjoern A. Zeeb wrote: > >> On 30 Jul 2014, at 07:19 , Edward Tomasz Napierała wrote: > >> > >>> At the link below you will find a patch that adds the new automounter. > >>> The patch is against yesterdays 11.0-CURRENT. > >>> > >>> http://people.freebsd.org/~trasz/autofs-head-20140729.diff > >> > >> I also just submitted https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192379 to allow -o vers= mount_nfs compatibility, which makes it easier to integrate with Linux/OSX/Solaris LDAP setups and mount options from LDAP. > > > > Nice! Will you commit it? > > Yeah and MFC for 10.1 unless someone speaks up the next day or two. I have updated the man page locally and I emailed Rick Macklem; will see if he’s around. Thanks! > >>> Testing is welcome. Please start with manual pages, eg. automount(8). > >> > >> > >> I found one case now doing the aforementioned where when the initial mount_nfs fails (e.g., for invalid options), then a later mount did not succeed either, with the correct mount options; I did try to run automount -u in between tries, as well as service automountd restart, but that did not make a change; given I was short on time, a reboot of my desktop made this go away. Is there some “negative caching” in the kernel module possibly that will not retry the mount for another time or something—as in if I were more patient and waited 5 minutes, would it maybe just have worked again? > > > > There is no negative caching. I'll see if I can figure out the cause > > for this. > > Thanks. I can possibly try to do some more tracing and debugging later in the week if needed. Ok. Now, to make sure I get it right: at first, the trigger failed, because of invalid mount options in map. The filesystem didn't get mounted, and the command that triggered the mount returned some kind of Input/Output Error. After fixing the map and trying to access the same directory again... what exactly happened at this point? In what way exactly did the second mount fail?