Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 May 2016 14:08:15 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        Edward Tomasz Napiera?a <trasz@FreeBSD.org>
Cc:        FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   Re: r298143: something wrong with autofs?
Message-ID:  <20160506140815.4974bf83.ohartman@zedat.fu-berlin.de>
In-Reply-To: <20160504184151.GA12165@brick>
References:  <20160417105741.170f6f14.ohartman@zedat.fu-berlin.de> <20160417103944.GA30972@brick.home> <20160503184950.15e58c87.ohartman@zedat.fu-berlin.de> <20160504184151.GA12165@brick>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
Am Wed, 4 May 2016 20:41:51 +0200
Edward Tomasz Napiera?a <trasz@FreeBSD.org> schrieb:

> On 0503T1849, O. Hartmann wrote:
> > Am Sun, 17 Apr 2016 12:39:44 +0200
> > Edward Tomasz NapieraƂa <trasz@FreeBSD.org> schrieb:
> >   
> > > On 0417T1057, O. Hartmann wrote:  
> > > > 
> > > > Running FreeBSD 11.0-CURRENT #32 r298143: Sun Apr 17 09:48:26 CEST 2016  amd64, on
> > > > both server and client, reveals today that AUTOFS seems not to work. Did something
> > > > changed unnoticed?
> > > > 
> > > > I realized, that no exported filesystem is bound so far. On the server's side,
> > > > all    
> > > 
> > > "Bound"?  
> > 
> > ... means: the cleint does not mount/bind the NFS exported filesystem anymore.  
> 
> Ok.
> 
> > > > daemons necessary are configured as they were before in a working state and as I
> > > > can see so far, they are up and running and also listening to their
> > > > sockets/IPs.     
> > > 
> > > Could you describe in more detail what are you seeing?  Also, the usual autofs
> > > debugging technique ("pkill automountd && while :; do automountd -d; done") might
> > > sched some light.  
> > 
> > Well, I see nothing! That is my problem. I setup several NFSv4 exported filesystems
> > which were mounted on demand via autofs - that workd. Since I do not use/need those
> > filesystems on a dailt basis, I realized too late that in the meanwhile those
> > filesystems are not present on the client (autofs) anymore. I'm not aware of having
> > changed anything in the configuration and I didn't receive any heads-ups that
> > essential changes had been made.  
> 
> Hm, it certainly seems weird.  Are the autofs instances mounted where
> there should be?  Could you send me your /etc/auto_master, the maps,
> and dmesg output?  Thanks!

Hello Edward,

sorry for the late answer. I can not (I'm not allowed!) offer config data from any of the
lab's/bureaus computers, so I decided to check again the whole config, since several
boxes do as expected and others not (which is the weird part). I found a simple culprit:
somewhere in the near past, /etc/auto_master received an update and I simply have
overwritten the old one with the new one. So the autofs system never checked the exported
filessystem's list given by a mandatory /etc/auto_ext file and in the logical consequence,
no filesystem defined there was mounted.

After simply adding the missing line the mounting of the expected filesystems worked
again.

Kind regards,
Oliver
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXLIkvAAoJEOgBcD7A/5N81IUH/RLo1u8yAVLUfx/pykO7TuTF
SR2WCDlgZvB+xfvvXJ05MYz20pA7HmdwE+zoGJ5Wy/144sxbjj6sH7j1pG9++pL4
x7D7kg5EQE+KyvZmcqLyJA0KjilnHSzN1P3hQUgtmp38P1UuF8zYjIZHg41bojEn
rXJMLlO9/IBqEuJhfHP8lM3+RdDDdqbY21+E0zLKVpb3InbsBIRUacTCRYoqM4lO
gA+kTZAMCePtT2xTm09i6XjVvG9aGmx13+43olLU6SRH5qM3FHNTo6NMkmz0RhsA
hH5VoGb9ej634F/GLhWylX1cZAds+1W0SGCJOc68lM+bxMNzfJ69Im3f973biqs=
=wRca
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160506140815.4974bf83.ohartman>