Bug 17540

Summary:	[nfs] NIS host lookups cause NFS mounts to wedge at boot
Product:	Base System	Reporter:	Andrew Gallatin <gallatin>
Component:	conf	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed Overcome By Events
Severity:	Affects Only Me	CC:	hiren
Priority:	Normal
Version:	4.0-RELEASE
Hardware:	Any
OS:	Any

Description Andrew Gallatin 2000-03-22 00:10:01 UTC

Portmap is not started until until the pass2 portion of rc.network is
executed. However, network_pass2 is run after we mount NFS
filesystems.

This is problematic in some environments if you have have nis as one
of the 1st entries in the host search order in /etc/host.conf.  The
problem is that the resolver cannot contact portmap to realize that
ypbind isn't available.  So the machines sits at 
	Mounting NFS file systems.
for quite some time.  Long enough for somebody to assume the machine
is wedged.

Fix: 

Start portmap before attempting any NFS mounts.

I suppose a shorter timeout when portmap cannot be contacted would
also be a good fix.
How-To-Repeat: 
Change /etc/host.conf so that nis is first in the search order, add an 
nfs mount to /etc/fstab, reboot.

Comment 1 Mike Barcroft freebsd_committer

2001-07-22 01:51:42 UTC

State Changed
From-To: open->feedback


Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE?

Comment 2 Mike Barcroft freebsd_committer

2001-07-26 04:40:35 UTC

Adding to Audit-Trail.

----- Forwarded message from Andrew Gallatin <gallatin@cs.duke.edu> -----

X-UIDL: 36c6b831b2c06bf0936f0a934146d098
Delivered-To: mike@freebsd.org
From: Andrew Gallatin <gallatin@cs.duke.edu>
Date: Tue, 24 Jul 2001 12:28:04 -0400 (EDT)
To: mike@FreeBSD.org
Cc: freebsd-bugs@FreeBSD.org
Subject: Re: conf/17540: NIS host lookups cause NFS mounts to wedge at boot
In-Reply-To: <200107220052.f6M0qIG35244@freefall.freebsd.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid


mike@FreeBSD.org writes:
 > Synopsis: NIS host lookups cause NFS mounts to wedge at boot
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: mike
 > State-Changed-When: Sat Jul 21 17:51:42 PDT 2001
 > State-Changed-Why: 
 > 
 > Does this problem still occur in newer versions of FreeBSD,
 > such as 4.3-RELEASE?
 > 
 > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17540

I believe so, yes.  And it turns out that rpc.umntall can also be a
problem for similar reasons.

FreeBSD 4.3-RELEASE #0: Tue Jul 10 11:44:28 EDT 2001
    gallatin@brahms.cs.duke.edu:/.amd_mnt/grapefruit/export/ari_scratch3/gallatin/4.3/sys/compile/ZCALPHA
ST6600
COMPAQ Professional Workstation XP1000, 500MHz
8192 byte page size, 1 processor.
<...>
add net default: gateway 152.3.145.61
Additional routing options: TCP keepalive=YES.
routing daemons:.
Mounting NFS file systems^Tload: 0.06  cmd: rpc.umntall 75 [select] 0.00u 0.00s 0% 1000k
^Tload: 0.04  cmd: rpc.umntall 75 [select] 0.00u 0.00s 0% 1000k
^Tload: 0.01  cmd: rpc.umntall 75 [select] 0.00u 0.01s 0% 1040k

<or, after replacing rpc.umntall with /usr/bin/true>

Mounting NFS file systems^Tload: 0.04  cmd: mount_nfs 75 [select] 0.00u 0.00s 0% 392k
^Tload: 0.04  cmd: mount_nfs 75 [select] 0.00u 0.00s 0% 392k
^Tload: 0.04  cmd: mount_nfs 75 [select] 0.00u 0.00s 0% 392k

Cheers,

Drew


----- End forwarded message -----

Comment 3 Mike Barcroft freebsd_committer

2001-07-26 04:46:17 UTC

State Changed
From-To: feedback->suspended


This is indeed still a problem.  Andrew's solutions sounds good. 
It should also probably be documented somewhere, if it isn't. 
Awaiting committer.

Comment 4 cel freebsd_committer

2006-05-13 01:06:24 UTC

Responsible Changed
From-To: freebsd-bugs->cel

Comment 5 cel freebsd_committer

2007-03-12 15:26:15 UTC

Responsible Changed
From-To: cel->freebsd-bugs

Back to the public pool. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=17540 

[bugmeister note: possibly related to conf/22308]

Comment 6 Hiren Panchasara freebsd_committer

2017-01-06 00:59:54 UTC

Been quite some time. Please reopen if this is still a problem.