NetBSD Problem Report #18782
Received: (qmail 3745 invoked by uid 605); 23 Oct 2002 01:55:22 -0000
Message-Id: <200210230150.g9N1oEH03259@mail.neutralgood.org>
Date: Tue, 22 Oct 2002 21:50:14 -0400 (EDT)
From: kpneal@pobox.com
Sender: gnats-bugs-owner@netbsd.org
Reply-To: kpneal@pobox.com
To: gnats-bugs@gnats.netbsd.org
Subject: 1.6 NFS client reports server failure too easily
X-Send-Pr-Version: 3.95
>Number: 18782
>Category: kern
>Synopsis: 1.6 NFS client reports server failure too easily
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Oct 23 01:56:00 +0000 2002
>Closed-Date: Tue May 01 00:00:59 +0000 2012
>Last-Modified: Tue May 01 00:00:59 +0000 2012
>Originator: Kevin P. Neal
>Release: NetBSD 1.6
>Organization:
none
>Environment:
System: NetBSD tome.neutralgood.org 1.6 NetBSD 1.6 (TOME-$Revision: 1.2 $) #0: Mon Oct 21 00:02:38 EDT 2002 kpn@neutralgood.org:/local/kernel/compile/TOME alpha
>Description:
Seen in my syslog (both machines are Alpha's running 1.6):
Oct 20 03:02:51 tesseract /netbsd: nfs server tome:/local: not responding
Oct 20 03:02:51 tesseract /netbsd: nfs server tome:/local: is alive again
Oct 20 04:02:54 tesseract /netbsd: nfs server tome:/local: not responding
Oct 20 04:02:54 tesseract /netbsd: nfs server tome:/local: is alive again
Oct 20 05:17:54 tesseract /netbsd: nfs server tome:/local: not responding
Oct 20 05:17:54 tesseract /netbsd: nfs server tome:/local: is alive again
Oct 20 10:03:07 tesseract /netbsd: nfs server tome:/local: not responding
Oct 20 10:03:07 tesseract /netbsd: nfs server tome:/local: is alive again
Oct 20 22:48:08 tesseract /netbsd: nfs server tome:/local: not responding
Oct 20 22:48:08 tesseract /netbsd: nfs server tome:/local: is alive again
This didn't happen when tesseract (the client) was running 1.5.2 or
earlier. It seems to match times when tome happens to be really busy,
but it also might be due to my slow network (10base-T).
The server (tome) is a:
AlphaStation 200 4/233, 233MHz
8192 byte page size, 1 processor.
total memory = 65536 KB
The client (tesseract) is a:
Alpha PC AXPpci33, 166MHz, s/n
8192 byte page size, 1 processor.
total memory = 49152 KB
Yes, that means the client is much slower than the server.
Note that I have no reason to believe the problem is specific to
the Alpha. That's just all I have running.
>How-To-Repeat:
Upgrade 6+ year old Alphas to NetBSD 1.6. Have filesystems NFS
exported from one box and mounted to another. Make server busy,
network loaded, whatever. Enjoy spam in your dmesg and syslog.
>Fix:
Dunno.
>Release-Note:
>Audit-Trail:
From: Ed Gould <ed@left.wing.org>
To: gnats-bugs@gnats.netbsd.org
Cc:
Subject: Re: kern/18782: 1.6 NFS client reports server failure too
easily
Date: Tue, 22 Oct 2002 22:42:24 -0700
> This didn't happen when tesseract (the client) was running 1.5.2 or
> earlier. It seems to match times when tome happens to be really busy,
> but it also might be due to my slow network (10base-T).
I see the same symptoms with an Alpha client running 1.6 and an x86
server running 1.5.
--Ed
From: fredb@immanent.net (Frederick Bruckman)
To: kpneal@pobox.com
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/18782: 1.6 NFS client reports server failure too easily
Date: Wed, 23 Oct 2002 08:56:27 -0500 (CDT)
In article <200210230150.g9N1oEH03259@mail.neutralgood.org>,
kpneal@pobox.com writes:
>
> Seen in my syslog (both machines are Alpha's running 1.6):
>
> Oct 20 03:02:51 tesseract /netbsd: nfs server tome:/local: not responding
> Oct 20 03:02:51 tesseract /netbsd: nfs server tome:/local: is alive again
> Note that I have no reason to believe the problem is specific to
> the Alpha. That's just all I have running.
It's not. I see a lot of these with my incredibly slow server, too:
486vlb, dx4-100, 16mb, with a similar client, and with an Armada M700
laptop. It usually only does it when first connecting, or when first
accessing the file system after some idle time (perhaps until "nfsd"
and "mountd" are paged in?).
I've given some thought to experimenting with "-d -t N" on the clients,
but it's not clear, from mount_nfs(8), whether this even has an effect
with TCP mounts, or what sort of values you might use for "NNN".
--
Frederick
State-Changed-From-To: open->feedback
State-Changed-By: pooka@NetBSD.org
State-Changed-When: Tue, 29 Jun 2010 19:09:27 +0300
State-Changed-Why:
is this still an issue in any supported release?
State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Tue, 01 May 2012 00:00:59 +0000
State-Changed-Why:
I certainly have not seen this problem in a long time, ever since
nfs cleanup probably 8-10 years ago.
>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.