Date: Mon, 23 Nov 1998 10:13:49 -0800 (PST) From: Tom Bartol <bartol@salk.edu> To: John Polstra <jdp@polstra.com> Cc: current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) Message-ID: <Pine.BSF.3.96.981123100100.22599B-100000@eccles.salk.edu> In-Reply-To: <XFMail.981119161749.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 19 Nov 1998, John Polstra wrote: > On 20-Nov-98 Tom Bartol wrote: > > > > Thanks for the info. I'll try it out tomorrow. If I want NFSv3 with UDP > > I suppose I would say: > > > > proto=udp,vers=3 > > > > correct? > > Correct. I had problems using NFSv3 the last time I tried it, but > that was several months ago. Maybe it's better now. > > > BTW, I can't find these options documented in amd(8) amd.conf(5) or > > mount_nfs(8). Any place else I should be looking? > > Not that I know of. The documentation is pretty broken. I had a > very hard time even finding the right options in the sources. > > John > --- With many thanks to your expert advice the proto=udp,vers=3 options to amd gets NFS mounts working reliably with amd for me again. However, I only get ~4MBps throughput to and NFSv3 mounted filesystem when amd makes the mount for me, but I get ~9MBps throughput when I mount the same filesystem by hand (i.e. without amd). The /defaults line in may amd.map file looks like: /defaults type:=nfs;opts:=rw,proto=udp,vers=3 My first guess at the reason would be that amd is mounting with very different default options than those built into mount_nfs but I'm having a lot of trouble narrowing down which of the myriad mount options are to blame here and (more importantly) which options amd is using as its defaults. Does anyone have any help to offer me on this one? Thanks again, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981123100100.22599B-100000>