From owner-freebsd-stable@FreeBSD.ORG Thu Sep 9 13:31:53 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC97A10656CB for ; Thu, 9 Sep 2010 13:31:53 +0000 (UTC) (envelope-from O.Seibert@cs.ru.nl) Received: from rustug.science.ru.nl (rustug.science.ru.nl [131.174.16.158]) by mx1.freebsd.org (Postfix) with ESMTP id 4FDA28FC1C for ; Thu, 9 Sep 2010 13:31:52 +0000 (UTC) Received: from kookpunt.science.ru.nl (kookpunt.science.ru.nl [131.174.30.61]) by rustug.science.ru.nl (8.13.7/5.31) with ESMTP id o89DAK3t015605 for ; Thu, 9 Sep 2010 15:10:20 +0200 (MEST) Received: from twoquid.cs.ru.nl (twoquid.cs.ru.nl [131.174.142.38]) by kookpunt.science.ru.nl (8.13.7/5.31) with ESMTP id o89DAHfA000284; Thu, 9 Sep 2010 15:10:17 +0200 (MEST) Received: by twoquid.cs.ru.nl (Postfix, from userid 4100) id CC0E52E04F; Thu, 9 Sep 2010 15:10:17 +0200 (CEST) Date: Thu, 9 Sep 2010 15:10:17 +0200 From: Olaf Seibert To: freebsd-stable@freebsd.org Message-ID: <20100909131017.GO4404@twoquid.cs.ru.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) X-Spam-Score: -1.799 () ALL_TRUSTED,BAYES_50 X-Scanned-By: MIMEDefang 2.63 on 131.174.30.61 Subject: mountd has resolving problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Sep 2010 13:31:53 -0000 I just upgraded a box from 8.0 to 8.1, and already when rebooting with the new kernel (i.e. before installing new userland), I got the following problem. Of course many of the messages scrolled off screen, but some were preserved in the syslog. Sep 9 14:26:51 fourquid mountd[839]: can't get address info for host XYZ Sep 9 14:26:51 fourquid mountd[839]: bad host XYZ in netgroup vbgroup, skipping Mountd was run and wanted to determine which hosts to export to. However, it could not resolve any of them. So, that suggests some network issue. However, I use a static IP address (no DHCP) and static info in /etc/resolv.conf, using one of the university's name servers. So resolving should always be available. Running /etc/rc.d/mountd restart so far always solved the export problem. I have also seen (presumably similar) issues with mounting NFS file systems, but that was deemed so fatal that the boot was aborted. A mount ``by hand'' of the affected file system also worked. Any ideas? Maybe with the new kernel the network interface is a bit slower in coming up, and not fully working by the time /etc/rc.d/mountd runs? In fact, I now notice this sequence of messages in /var/log/messages: Sep 9 14:26:51 fourquid mountd[839]: bad host XYZ in netgroup vbgroup, skipping Sep 9 14:26:51 fourquid mountd[839]: bad exports list line /xxxxxx Sep 9 14:26:54 fourquid kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Sep 9 14:26:54 fourquid init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Sep 9 14:26:55 fourquid kernel: nfe0: link state changed to UP so here the network interface takes a full 4 more seconds to come up, after it was already needed. I can try to put a 10 sec delay somewhere, but there should be a better solution... -Olaf. --