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!uwm.edu!feeder.chicago.cic.net!news.maxwell.syr.edu!news.mathworks.com!news.eecs.umich.edu!life.eecs.umich.edu!not-for-mail From: pmchen@life.eecs.umich.edu (Peter M. Chen) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Help with FreeBSD 2.2.2-RELEASE NFS/automounter problem Date: 4 Jun 1997 04:55:50 GMT Organization: University of Michigan EECS Lines: 21 Message-ID: <5n2sgm$bl2$1@news.eecs.umich.edu> References: <5n05bh$2ci$1@scorpion.broadcom.com> <5n1cf7$k04$1@news.eecs.umich.edu> <5n2c22$3m1$1@scorpion.broadcom.com> NNTP-Posting-Host: 141.213.8.32 X-Newsreader: TIN [UNIX 1.3 950824BETA PL0] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42268 John Sin (jsin@scorpion.broadcom.com) wrote: >What kind of problems do you have? At least for me, I haven't seen a >problem with NFS in general; only when I'm re-mounting local file system >via NFS. 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). >I did some more testing, and now it appears that the problem doesn't >involve amd at all. > >Here's what I did: > mount localhost:/ /mnt > cp /tmp/bigfile /mnt/tmp/bigfile.copy I believe youu're describing the infamous packet overrun problem. Check the handbook under "Advanced networking". Pete