Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!news.netspace.net.au!news.mira.net.au!news.vbc.net!vbcnet-west!garlic.com!fox.almaden.ibm.com!uunet!in2.uu.net!206.229.87.25!news.sprintlink.net!news-peer.sprintlink.net!news-pull.sprintlink.net!news.sprintlink.net!news-dc-9.sprintlink.net!news.aloha.net!news-w.ans.net!newsfeeds.ans.net!lantana.singnet.com.sg!peony.singnet.com.sg!nuscc.nus.sg!iss.nus.sg!not-for-mail From: kongwah@iss.nus.sg (Wan Kong Wah) Newsgroups: comp.unix.bsd.freebsd.misc Subject: 2 NFS problem Date: 25 Feb 1997 09:38:16 GMT Organization: Institute Of Systems Science, National University Of Singapore. Lines: 23 Message-ID: <5eubu8$4tf@holodeck.iss.nus.sg> NNTP-Posting-Host: otter.iss.nus.sg X-Newsreader: TIN [UNIX 1.3 950824BETA PL0] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36078 Hi, 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. When using rcp instead, it is faster at 0.6s. Hence the underlying tcpip connection (cabling, etc) is OK. Could it have to do with the local freebsd NFS client buffering/caching? How to test and set properly? Also, another Linux machine which reads from the DEC file system is reading old copies, possibly from its local cache. The DEC server has its NFS "properly" setup, with NFSD set to 8 and NFSIOD set to 7. With 64MB ram, it is more than enough to service NFS requests from just 2 machines. So all things point to an improper NFS client setup on the freebsd and linux machines. Appreciate any suggestions and help, Kind regards, Kong Wah