Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!howland.erols.net!newsxfer.itd.umich.edu!news.ececs.uc.edu!news.kei.com!news.thenet.net!uunet!in2.uu.net!199.232.240.7!kayrad.ziplink.net!ejon_ppp From: ejon@ziplink.net (Eric Jones) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 2 NFS problem Date: Tue, 04 Mar 97 05:35:17 GMT Organization: ZipLink -- America's Hottest ISP Lines: 35 Message-ID: <5ffqm3$i38$1@kayrad.ziplink.net> References: <5eubu8$4tf@holodeck.iss.nus.sg> <5fcpoe$8u@uriah.heep.sax.de> NNTP-Posting-Host: bos-ip-1-21.ziplink.net X-Newsreader: News Xpress 2.0 Beta #2 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36479 In article <5fcpoe$8u@uriah.heep.sax.de>, joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) wrote: >kongwah@iss.nus.sg (Wan Kong Wah) wrote: > >> I have a freebsd machine which writes VERY slowly to an >> remote NFS directory exported from a DEC server machine. >> A simple cp of 400Kbytes take 4-5 seconds. > >That's probably not a very unusual value. With NFSv2, the server must >ensure the data have been written ``to stable storage'' before it is >allowed to return from the NFS write call. I've seen rates of 150 or >200 KB/s, but not much more. > [some text elided] > >If your FreeBSD system is 2.2 or higher, you might give NFSv3 a try. There are some known interoperability problems with the NFSv3 implementation on Digital UNIX. My memory is somewhat sketchy on this point, but I believe the symptoms include wedged nfsd processes and possibly progressively decreasing performance. > >> Also, another Linux machine which reads from the DEC file >> system is reading old copies, possibly from its local cache. > >That's either a bug in Linux's implementation, or (less likely) of the >server machine. > Well, I saw similar effects when trying to use leasing under nqnfs under Freebsd 2.1mumble (that is, between two such machines). When I took the -L's and -k's out of my mount commands, I stopped seeing it. Try a _very_ simple mount and performance be damned...this _is_ nfs, after all. Eric