From owner-freebsd-current Thu Nov 19 14:22:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28150 for freebsd-current-outgoing; Thu, 19 Nov 1998 14:22:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28135 for ; Thu, 19 Nov 1998 14:22:29 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA29388; Thu, 19 Nov 1998 14:21:10 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA09145; Thu, 19 Nov 1998 14:21:09 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 19 Nov 1998 14:21:09 -0800 (PST) Message-Id: <199811192221.OAA09145@vashon.polstra.com> To: bartol@salk.edu Subject: Re: Problem with amd (was: NFS problems in -current) Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Tom Bartol wrote: > > O.K. Here's another big clue. I had been mounting using amd. If I mount > without amd then all is well and performance is much better also. I now > get ~9MBps instead of ~4MBps over a 100BT segment. Aha! The new amd uses different options to select the protocol for NFS. I bet you still have an old amd.map file. For the new amd, the desired options are "proto=udp,vers=2". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message