From owner-freebsd-current Fri Aug 15 10:25:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA07529 for current-outgoing; Fri, 15 Aug 1997 10:25:25 -0700 (PDT) Received: from lamb.sas.com (daemon@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA07468 for ; Fri, 15 Aug 1997 10:24:12 -0700 (PDT) Received: from mozart by lamb.sas.com (5.65c/SAS/Gateway/01-23-95) id AA04289; Fri, 15 Aug 1997 13:23:36 -0400 Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA14375; Fri, 15 Aug 1997 13:19:37 -0400 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA22964; Fri, 15 Aug 1997 13:19:37 -0400 Message-Id: <199708151719.AA22964@iluvatar.unx.sas.com> Subject: More nfs issues against -current To: freebsd-current@freebsd.org Date: Fri, 15 Aug 1997 13:19:36 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, A few days ago I posted about nfs v2 vs. nfs v3 and some serious performance degradation. This is against the lastest -current source. 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 This has been going on now for about 2 hours. The netapp01 machine is fine. I can copy the files in question to my HP workstation, or my NT workstation, without any problems. ie: under hpux: jwd %timex cp X33* /tmp real 55.02 user 0.15 sys 6.43 So, nfs v3 locks up for 30 minute intervals on me, and v2 appears to "flakey". Does anyone have any ideas on what the problem might be, or where I should start looking? Thanks, John -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915