From owner-freebsd-current Tue Aug 12 12:36:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA13610 for current-outgoing; Tue, 12 Aug 1997 12:36:12 -0700 (PDT) Received: from lamb.sas.com (uucp@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA13605 for ; Tue, 12 Aug 1997 12:36:07 -0700 (PDT) Received: from mozart by lamb.sas.com (5.65c/SAS/Gateway/01-23-95) id AA11277; Tue, 12 Aug 1997 15:35:59 -0400 Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA16125; Tue, 12 Aug 1997 15:35:49 -0400 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA08461; Tue, 12 Aug 1997 15:35:49 -0400 Message-Id: <199708121935.AA08461@iluvatar.unx.sas.com> Subject: NFS V3 hangs To: current@freebsd.org Date: Tue, 12 Aug 1997 15:35:48 -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, I have the latest -current snap loaded. I am using NFS to access a network appliance fileserver (which supports V3). The response time of doing an ls is non-trivial. cd targetdir (which contains 686 files) time ls returns 0.0u 0.0s 16:40.49 0.0% 704+1024k 0+0io 0pf+0w Ok, so I umount the directory and remount with the -2 option: cd targetdir (which contains 686 files) time ls returns 0.0u 0.0s 0:02.84 0.7% 78+170k 0+0io 0pf+0w Is this a known bug? And if not, what can I do to help solve the problem? I would really like to be able to use NFS V3 in this situation. FWIW: mount_nfs -U doesn't make any difference. Thanks! John -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915