From owner-freebsd-questions@FreeBSD.ORG  Wed Feb 11 07:55:42 2009
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A6B041065678
	for <freebsd-questions@freebsd.org>;
	Wed, 11 Feb 2009 07:55:42 +0000 (UTC)
	(envelope-from fbsd.questions@rachie.is-a-geek.net)
Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27])
	by mx1.freebsd.org (Postfix) with ESMTP id 713038FC19
	for <freebsd-questions@freebsd.org>;
	Wed, 11 Feb 2009 07:55:41 +0000 (UTC)
	(envelope-from fbsd.questions@rachie.is-a-geek.net)
Received: from localhost (mail.lan.rachie.is-a-geek.net [192.168.2.101])
	by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 50CB8AFC206;
	Tue, 10 Feb 2009 22:55:41 -0900 (AKST)
From: Mel <fbsd.questions@rachie.is-a-geek.net>
To: freebsd-questions@freebsd.org
Date: Tue, 10 Feb 2009 22:55:41 -0900
User-Agent: KMail/1.9.10
References: <FC5FF0B613540249959195342B6D034C754785@worldmax-sbs01.Worldmax.local>
	<200901301142.34624.fbsd.questions@rachie.is-a-geek.net>
	<FC5FF0B613540249959195342B6D034C7D20D8@worldmax-sbs01.Worldmax.local>
In-Reply-To: <FC5FF0B613540249959195342B6D034C7D20D8@worldmax-sbs01.Worldmax.local>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200902102255.41098.fbsd.questions@rachie.is-a-geek.net>
Cc: Arjan van der Oest <arjan.van.der.oest@worldmax.nl>
Subject: Re: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs during
	mountcritremote execution
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2009 07:55:43 -0000

On Tuesday 10 February 2009 01:34:47 Arjan van der Oest wrote:
> Hi Mel,
>
> Sorry for not getting back to you earlier, I have been out of the office
> for some time...
>
> > Does this one also have a link UP message after nfs mounting? If not,
>
> then
>
> > there's your culprit: network isn't up at mountcritremote time. You
>
> should
>
> > mark it 'late' in fstab
>
> The UP message came more or less at the same time. Marking it late fixed
> the problem, still leaving me puzzled why the NFS mounts work without
> problem on identical machines but not in this one. Anyhow, since it's
> not a critical fs, the late option works fine.

There's 2 scenarios for late NFS mounting:
- local named: named gets started after mountcritremote, fixable with 
resolv.conf that has an additional nameserver or populate /etc/hosts.
- slow network card and/or DHCP server causing the network card to be down or 
without IP address / invalid resolv.conf at mountcritremote. Not really 
fixable.

-- 
Mel

Problem with today's modular software: they start with the modules
    and never get to the software part.