From owner-freebsd-current Thu Nov 19 00:32:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28649 for freebsd-current-outgoing; Thu, 19 Nov 1998 00:32:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28644 for ; Thu, 19 Nov 1998 00:32:49 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA13739; Thu, 19 Nov 1998 08:33:40 GMT Date: Thu, 19 Nov 1998 08:33:39 +0000 (GMT) From: Doug Rabson To: Tom Bartol cc: freebsd-current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, 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. > > So, I know we are now using a newer version of amd. This version seems to > be causing me lots of problems. Is anyone else out there experiencing > this??? I guess that amd must be using different options to mount with. The brute force to figuring that out would be to put some code in amd to print out the NFS mount options it is going to use and then compare that to mount_nfs. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message