Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.edu.au!news.apana.org.au!cantor.edge.net.au!news.teragen.com.au!news.access.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news.maxwell.syr.edu!news.apfel.de!news-fra1.dfn.de!news-ber1.dfn.de!news-lei1.dfn.de!news.urz.tu-dresden.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 2 NFS problem Date: 2 Mar 1997 20:59:58 GMT Organization: Private BSD site, Dresden Lines: 39 Message-ID: <5fcpoe$8u@uriah.heep.sax.de> References: <5eubu8$4tf@holodeck.iss.nus.sg> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36456 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. For small files, the nfsiod's on the client machine help out of this dilemma. With NFSv3, matters are different, since there's an official way to do asynchronous writes. Some NFSv2 implementations (like SGI IRIX) are cheating, and perform async writes even in v2. This violates the specs unless the machine can otherwise guarantee the delayed write will indeed succeed (which requires at least an UPS, plus an operating system that never crashes). (FreeBSD offers this behaviour as an option, for those who know what they are doing when they turn it on. However, this won't help you, since it's a server problem, not a client problem.) If your FreeBSD system is 2.2 or higher, you might give NFSv3 a try. > 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. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)