Date: Fri, 26 Sep 2014 12:32:27 +0200 From: Hans Ottevanger <hans@beastielabs.net> To: =?UTF-8?B?RWR3YXJkIFRvbWFzeiBOYXBpZXJhxYJh?= <trasz@FreeBSD.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Fwd: Autofs: spurious (?) log messages and zombies from automountd Message-ID: <542540BB.80001@beastielabs.net> In-Reply-To: <20140926090053.GA10644@brick.home> References: <54226E4D.1040704@beastielabs.net> <54250A50.1000607@beastielabs.net> <20140926090053.GA10644@brick.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/26/14 11:00, Edward Tomasz Napierała wrote: > On 0926T0840, Hans Ottevanger wrote: >> Reposting here (with typos in subject corrected) after no response from >> stable@ for almost two days. >> >> Regards, >> >> Hans >> >> >> -------- Forwarded Message -------- >> Subject: Aitofs: spurious (?) jog messages and zombies from automountd >> Date: Wed, 24 Sep 2014 09:10:05 +0200 >> From: Hans Ottevanger <hans@beastielabs.net> >> To: freebsd-stable@FreeBSD.org >> >> Hi, >> >> When accessing a directory for the first time on /net, automounted using >> the new autofs, I reproducibly get error messages in the log. >> >> I have exported a single directory (read/write) from my test server: >> >> $ showmount -e soekris >> >> Exports list on soekris: >> /home >> >> My client runs 10-STABLE, also known as 10.1-BETA2 these days, updated >> to r272021. The kernel config is GENERIC minus devices that I do not >> have, with AUTOFS added. >> >> When accessing the server for the first time using: >> >> ls /net/soekris/home/hans >> >> I get the expected directory listing but immediately also see the >> following in /var/log/messages: >> >> Sep 24 07:39:09 beastie automountd[1554]: child process 2096 terminated >> with exit status 1 >> Sep 24 07:39:09 beastie automountd[1554]: child process 2101 terminated >> with exit status 1 > > There are no log messages preceding this? > No. Just the normal messages logged at boot time. >> Additionally, a zombie process keep hanging forever: >> >> $ pstree 1554 >> -+= 01554 root /usr/sbin/automountd >> \--- 02106 root <defunct> >> >> When I wait until the directory is autounmounted and retry the access, >> the zombie disappears (apparently finally waited for) and I get two >> others in return: >> >> $ pstree 1554 >> -+= 01554 root /usr/sbin/automountd >> |--- 02658 root <defunct> >> \--- 02663 root <defunct> >> >> and a few extra log messages: >> >> Sep 24 08:52:17 beastie automountd[1554]: child process 2106 terminated >> with exit status 1 >> Sep 24 08:52:17 beastie automountd[1554]: child process 2653 terminated >> with exit status 1 >> >> Is anyone else seeing this? >> Do I miss something? >> Is this expected behavior? > > Not quite; I'll try to reproduce it. > I planned to make a new CURRENT snapshot installation on another machine anyhow today. I will see what happens there. Kind regards, Hans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?542540BB.80001>