From owner-freebsd-current  Fri Aug 15 16:27:41 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA25059
          for current-outgoing; Fri, 15 Aug 1997 16:27:41 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25050
          for <freebsd-current@FreeBSD.ORG>; Fri, 15 Aug 1997 16:27:37 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA20894;
	Fri, 15 Aug 1997 16:29:14 -0700 (PDT)
Message-Id: <199708152329.QAA20894@implode.root.com>
To: "John W. DeBoskey" <jwd@unx.sas.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: More nfs issues against -current 
In-reply-to: Your message of "Fri, 15 Aug 1997 13:19:36 EDT."
             <199708151719.AA22964@iluvatar.unx.sas.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 15 Aug 1997 16:29:14 -0700
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>   Well, for the last few days, I've been running my current box with
>-2 on my mount points. Today, I tried to copy some seme-large files
>to my machine, and the system is putting the following out onto the
>console:
>
>nfs server netapp01:/home: not responding
>Aug 15, 12:54:41 mrose /kernel: nfs server netapp01:/home: not responding
>nfs server netapp01:/home: is alive again
>Aug 15, 12:55:17 mrose /kernel: nfs server netapp01:/home: is alive again
...
>   Does anyone have any ideas on what the problem might be, or where
>I should start looking?

   I think there is a bug in the timeout calculation. Try specifying a large
timeout value (see the -d and -t options in the mount_nfs man page).

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project