Date: Tue, 10 Feb 2009 22:55:41 -0900 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org 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 Message-ID: <200902102255.41098.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <FC5FF0B613540249959195342B6D034C7D20D8@worldmax-sbs01.Worldmax.local> References: <FC5FF0B613540249959195342B6D034C754785@worldmax-sbs01.Worldmax.local> <200901301142.34624.fbsd.questions@rachie.is-a-geek.net> <FC5FF0B613540249959195342B6D034C7D20D8@worldmax-sbs01.Worldmax.local>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200902102255.41098.fbsd.questions>