NetBSD Problem Report #9561
Received: (qmail 15156 invoked from network); 7 Mar 2000 15:27:59 -0000
Message-Id: <200003071527.KAA00616@wayne.mit.edu>
Date: Tue, 7 Mar 2000 10:27:57 -0500 (EST)
From: Dan McMahill <mcmahill@mtl.mit.edu>
Reply-To: mcmahill@mtl.mit.edu
To: gnats-bugs@gnats.netbsd.org
Subject: nfs client breaks
X-Send-Pr-Version: 3.95
>Number: 9561
>Category: bin
>Synopsis: nfs client fails, portmap fails
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: bin-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Mar 07 07:30:00 +0000 2000
>Closed-Date: Mon Sep 01 03:19:21 +0000 2008
>Last-Modified: Mon Sep 01 03:19:21 +0000 2008
>Originator: Dan McMahill
>Release: 1.4.1
>Organization:
none
>Environment:
System: NetBSD wayne.mit.edu 1.4.1 NetBSD 1.4.1 (WAYNE) #0: Sat Jan 8 15:00:10 EST 2000 mcmahill@wayne.mit.edu:/usr/src/sys/arch/i386/compile/WAYNE i386
(i386 and sparc)
>Description:
I have 3 NetBSD-1.4.1 machines (1-sparc, 2-i386) on a large network at school.
My home directory is on a solaris-2.6/sparc box and my mail directory is on
a solaris-2.7/sparc box. I use amd on the NetBSD machines to mount these
directories.
When the network goes down for a bit (a minute or 2), the NetBSD machines fail
to remount the mail directory and the boxes become unresponsive. I can,
however, log in at the console as root and reboot which fixes things. My
home directory, though, does properly remount.
My more detailed setup is:
lrwxrwxrwx 1 root wheel 25 Mar 7 10:17 /homes/mcmahill ->
/fs/bitter/home0/mcmahill
lrwxrwxrwx 1 root wheel 17 Mar 7 10:17 /fs/bitter/home0 ->
/amd/bitter/home0
bitter is solaris-2.6. This directory comes back up when the network
comes back.
and
lrwxr-xr-x 1 root wheel 7 Jan 5 21:02 /var/mail -> /u/mail
lrwxrwxrwx 1 root wheel 13 Mar 7 10:17 /u/mail -> /amd/mtl/mail
mtl is solaris-2.7. This directory doesn't come back when the network
comes back.
In addition, when the machine is in this unhappy state, if I try
amq -m
it responds with a portmap timeout.
>How-To-Repeat:
setup amd to nfs mount a directory from a solaris-2.7/sparc machine.
unplug the network for a bit, reattach the network, observe that the nfs
mounted directory doesn't come back.
>Fix:
I don't know of either a fix or a work around.
>Release-Note:
>Audit-Trail:
From: mcmahill@mtl.mit.edu
To: gnats-bugs@netbsd.org
Cc: Subject: bin/9561
Date: Wed, 8 Mar 2000 09:18:48 -0500 (EST)
Here are more settings for amd. It appears I use UDP, not TCP, for the
mounts.
oh, so its set by the NIS master in my case (which I also don't have
access to). For the (unreliable) mail server:
# ypcat -k u.amd | grep default
/defaults opts:=rw,intr,bg,grpid
# ypcat -k u.amd | grep mail
mail -type:=nfs;fs:=${autodir}/${rhost.}/${key};
opts:=rw,nosuid,bg,rsize=1024,wsize=1024,hard,intr,noac
host!=mtl;rhost:=mtl;rfs:=/var/mail
host==mtl;type:=link;fs:=/var/mail
for the (reliable) home directory server:
# ypcat -k homes.amd | grep default
/defaults type:=link;sublink:=${key};fs:=/fs/mtl-home/home0
# ypcat -k homes.amd | grep mcmahill
mcmahill fs:=/fs/bitter/home0
# ypcat -k fs.amd | grep default
/defaults opts:=rw,intr,bg,grpid,rsize=1024,wsize=1024;
type:=nfs;fs:=${autodir}/${key}
# ypcat -k fs.amd | grep "bitter/home0"
bitter/home0 host!=bitter;rhost:=bitter;rfs:=/export/home0
host==bitter;type:=link;fs:=/export/home0
-Dan
From: mcmahill@mtl.mit.edu
To: gnats-bugs@netbsd.org
Cc: Subject: bin/9561
Date: Wed, 8 Mar 2000 09:19:22 -0500 (EST)
---------- Forwarded message ----------
Date: Tue, 7 Mar 2000 19:16:35 -0500 (EST)
From: mcmahill@mtl.mit.edu
To: Matthias Scheler <tron@zhadum.de>
Subject: Re: bin/9561: nfs client breaks
On Wed, 8 Mar 2000, Matthias Scheler wrote:
> In article <200003071527.KAA00616@wayne.mit.edu>,
> Dan McMahill <mcmahill@mtl.mit.edu> writes:
> > When the network goes down for a bit (a minute or 2), the NetBSD machines
> > fail to remount the mail directory and the boxes become unresponsive.
>
> Do you use TCP or UDP mounts? If it's TCP try switching to UDP. The
> auto mount daemon in at least 1.4/1.4.x is know to have problems
> with TCP mounts.
hmm. I'm not really sure how to control this. Looking in
/var/log/amd.log, I see things like:
Mar 7 10:32:43 wayne amd[197]/info: Using NFS version 3, protocol udp on
host mtl.mit.edu
and
Mar 7 11:30:53 wayne amd[197]/info: Using NFS version 3, protocol udp on
host bitter.mit.edu
so I suppose this means its UDP? Where is this normally set?
Part of my troubles tracking this down is I don't have root or even an
enabled login account on the problem (solaris-2.7) server.
-Dan
From: mcmahill@mtl.mit.edu
To: gnats-bugs@netbsd.org
Cc:
Subject: bin/9561
Date: Tue, 9 May 2000 12:40:28 -0400 (EDT)
today, I saw the following on one of my xterms (this time a 1.4.2/sparc):
clnttcp_create: RPC: Port mapper failure - RPC: Timed out
then after that, I can't reach portmapper again:
ballast# amq -m
amq: failed to contact portmapper on host "localhost". RPC: Timed out
ballast# tcsh
ballast# ps -alx | grep port
0 161 1 0 2 0 128 600 select Ss ?? 1:05.62 portmap
-l
From: mcmahill@mtl.mit.edu
To: gnats-bugs@netbsd.org
Cc:
Subject: bin/9561
Date: Thu, 29 Jun 2000 15:07:28 -0400 (EDT)
a few more data points.
on 1.4.1 and 1.4.2 machines (I've tried i386,sparc, and pmax) at school,
the NIS master is a solaris (unknown version) box and my home directory is
NFS mounted (via amd) from a solaris box. Unplugging the network cable
for a minute or 2 will cause this bug. The only way to resume normal
operation is rebooting.
however at home where its all NetBSD-1.4.{1,2} machines (including the
NIS master and the file server), I can unplug one of the client machines
for a minute or 2 and it comes back the second I reattach the cable. If I
keep it unplugged for a longer time (I tried a couple of hours), then it
takes a little bit longer to come back, but still comes back.
-Dan
From: mcmahill@mtl.mit.edu
To: gnats-bugs@netbsd.org
Cc: soda@netbsd.org
Subject: bin/9561
Date: Sun, 16 Jul 2000 13:08:56 -0400 (EDT)
Hi,
I tried adding:
options NMBCLUSTERS=2048
to increase NMBCLUSTERS to see if that would help my network problems.
The problem is still there, but the symptoms have changed a little. When
my system got in a bad state before (with the default for NMBCLUSTERS),
'amq -m' would return:
amq: failed to contact portmapper on host "localhost". RPC: Timed out
now, I get:
amq: amd on localhost cannot provide mount info
a 'netstat -m' shows:
874 mbufs in use:
706 mbufs allocated to data
168 mbufs allocated to socket names and addresses
38/92 mapped pages in use
300 Kbytes allocated to network (61% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
so maybe this says I had 2 problems, one with portmap (which was helped
with more NMBCLUSTERS) and yet another with amd?
Any further thoughts?
-Dan
State-Changed-From-To: open->feedback
State-Changed-By: dholland@narn.netbsd.org
State-Changed-When: Sun, 20 Jan 2008 04:20:45 +0000
State-Changed-Why:
Does this still happen? All the pieces involved have been fixed repeatedly
in the interim...
State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 01 Sep 2008 03:19:21 +0000
State-Changed-Why:
Feedback timeout... and this is old enough, with components that get fixed
regularly, that we'll assume it's fixed.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.