From owner-freebsd-stable@FreeBSD.ORG Thu Feb 17 19:46:32 2011 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 D1486106566B; Thu, 17 Feb 2011 19:46:32 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx10.syd.optusnet.com.au (fallbackmx10.syd.optusnet.com.au [211.29.132.251]) by mx1.freebsd.org (Postfix) with ESMTP id 19E848FC14; Thu, 17 Feb 2011 19:46:31 +0000 (UTC) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by fallbackmx10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p1HHlKEl024342; Fri, 18 Feb 2011 04:47:20 +1100 Received: from c122-107-114-89.carlnfd1.nsw.optusnet.com.au (c122-107-114-89.carlnfd1.nsw.optusnet.com.au [122.107.114.89]) by mail04.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p1HHl4Qm001875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Feb 2011 04:47:05 +1100 Date: Fri, 18 Feb 2011 04:47:04 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: John Baldwin In-Reply-To: <201102171158.24636.jhb@freebsd.org> Message-ID: <20110218043432.S3233@besplex.bde.org> References: <20100909131017.GO4404@twoquid.cs.ru.nl> <20100909140529.GB76889@icarus.home.lan> <201102171158.24636.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Olaf Seibert , net@freebsd.org, freebsd-stable@freebsd.org, Jeremy Chadwick , Steven Hartland Subject: Re: 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, 17 Feb 2011 19:46:32 -0000 On Thu, 17 Feb 2011, John Baldwin wrote: > On Thursday, February 17, 2011 7:18:28 am Steven Hartland wrote: >> This has become a issue for us in 8.x as well. >> >> I'm pretty sure in pre 8.x these nfs mounts would simply background but >> recently machines are now failing to boot. It seems that failure to >> lookup nfs mount point hosts now causes this fatal error :( >> >> We've just tried Jeremy's netwait script and it works perfectly so either >> this or something similar needs to get pushed into base. >> >> For reference the reason we need a delay here is our core Cisco router >> takes a while to bring the port up properly on boot. >> >> Thanks for sharing the script Jeremy :) > > I use a similar hack that waits up to 30 seconds for the default gateway to be > pingable. I think it is at least partly related to the new ARP code that now > drops packets in IP output if the link is down. I use hackish ping -t s and traceroutes in /etc/rc.d/netif. Don't know if it is the same problem. It affects mainly nfs and ntpdate/ntpd to local systems here. Even with all-static routes. > This can be very problematic > during boot since some interfaces take a few seconds to negotiate link but > the end result of the new check in IP output is that the attempt to send the > packet fails with an error causing gethostbyname() and getaddrinfo() to fail > completely without doing any retries. In 7 the packet would either sit in the Also after down/up to change something. If you try to use the network before it is back then you have to wait much longer before it is really back. This is a relatively minor problem since down/up is not needed routinely. > descriptor ring until link was up, or it would be dropped, but it would > silently fail, so the resolver in libc would just retry in 30 seconds or so at > which time it would work fine. > > Waiting for the default route to be pingable actually fixed a few other > problems for us on 7 though as well (often ntpdate would not work on boot and > now it works reliably, etc.) so we went with that route. I thought I first saw the problem a little earlier, and it affected bge more than fxp. Maybe the latter is correct and the problem is smaller with fxp just because it is ready sooner. Bruce