Re: r298143: something wrong with autofs?

[Edward Tomasz Napiera?a]

On 0506T1408, O. Hartmann wrote:
> Am Wed, 4 May 2016 20:41:51 +0200
> Edward Tomasz Napiera?a  schrieb:
> 
> > On 0503T1849, O. Hartmann wrote:
> > > Am Sun, 17 Apr 2016 12:39:44 +0200
> > > Edward Tomasz Napierała  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.

Huh, that explains.  IIRC some time (few weeks?) ago there was a problem
in 11-CURRENT that made "make installworld" overwrite some of the config
files, as if there were binaries.  Looks like you got bitten by this.

Let me know if you find anything else with autofs that looks suspicious.
Thanks :-)

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: r298143: something wrong with autofs?

[O. Hartmann]

Am Wed, 4 May 2016 20:41:51 +0200
Edward Tomasz Napiera?a  schrieb:

> On 0503T1849, O. Hartmann wrote:
> > Am Sun, 17 Apr 2016 12:39:44 +0200
> > Edward Tomasz Napierała  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-unsubscr...@freebsd.org"


pgpzxe_9lg3VL.pgp
Description: OpenPGP digital signature

Re: r298143: something wrong with autofs?

[Edward Tomasz Napiera?a]

On 0503T1849, O. Hartmann wrote:
> Am Sun, 17 Apr 2016 12:39:44 +0200
> Edward Tomasz Napierała  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!

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: r298143: something wrong with autofs?

[O. Hartmann]

Am Sun, 17 Apr 2016 12:39:44 +0200
Edward Tomasz Napierała  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.

> 
> > 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.

> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"



pgpawDVp_f9k8.pgp
Description: OpenPGP digital signature

Re: r298143: something wrong with autofs?

[Edward Tomasz Napierała]

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"?

> 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.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"