Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!howland.erols.net!ix.netcom.com!fortress.broadcom.com!scorpion.broadcom.com!usenet From: jsin@scorpion.broadcom.com (John Sin) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Help with FreeBSD 2.2.2-RELEASE NFS/automounter problem Date: 4 Jun 1997 11:41:06 -0700 Organization: Broadcom Corporation Lines: 37 Message-ID: <5n4cs2$t3a$1@scorpion.broadcom.com> References: <5n05bh$2ci$1@scorpion.broadcom.com> <5n1cf7$k04$1@news.eecs.umich.edu> <5n2c22$3m1$1@scorpion.broadcom.com> <5n2sgm$bl2$1@news.eecs.umich.edu> NNTP-Posting-Host: scorpion.broadcom.com Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42351 In article <5n2sgm$bl2$1@news.eecs.umich.edu>, Peter M. Chen <pmchen@life.eecs.umich.edu> wrote: > >This was not an NFS problem--it's an amd problem. I had no problems manually >mounting the file systems. amdcomplains about "bad address" when it >attempts to mount. The amd that comes with 2.2.1-RELEASE works fine >(on both 2.2.1 and 2.2.2). Not to nitpick, but I didn't think version of amd had changed since oh, I don't know. My 2.2.2-RELEASE comes with amd 1.1.1.1 of 1994/05/26 05:22:08 bsd44 #0 and so does my 2.1.5-RELASE, and my 2.1.0-RELEASE. Granted, they each have been re-compiled under different OS, but the "amd -v" returns the same on all. >I believe youu're describing the infamous packet overrun problem. Check the >handbook under "Advanced networking". Nah, that's not it. Has anyone ever *seen* that problem in this day and age? :-) The problem is definitely with the NFSv3 implementation on 2.2.2-RELEASE. If I turn it off, then my problem goes away. So rather than doing mount -t nfs localhost:/ /mnt I do mount -t nfs -o -2 localhost:/ /mnt I had to RTFM on mount_nfs(8) under 2.2.2-RELEASE to figure this out. So, that makes me happy for now! Thanks to all.