Re: [CFT] Autofs.

On 0804T1635, Bjoern A. Zeeb wrote:
> 
> On 04 Aug 2014, at 16:17 , Edward Tomasz Napierała <trasz_at_freebsd.org> wrote:
> 
> > On 0804T1252, Bjoern A. Zeeb wrote:
> >> On 30 Jul 2014, at 07:19 , Edward Tomasz Napierała <trasz_at_freebsd.org> 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?