Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!swrinde!emory!wupost!csus.edu!netcom.com!alm From: alm@netcom.com (Andrew Moore) Subject: WD8003 r/wsize=4096? (was Re: cp/cpio over NFS unreliable? [386BSD]) Message-ID: <1992Nov13.233747.24435@netcom.com> Summary: -o rw,rsize=4096,wsize=4096 Organization: Netcom - Online Communication Services (408 241-9760 guest) References: <1992Nov12.085512.8850@netcom.com> Date: Fri, 13 Nov 1992 23:37:47 GMT Lines: 31 In article <1992Nov12.085512.8850@netcom.com> alm@netcom.com (Andrew Moore) writes: > > >cp'ing sbin/* across two NFS-mounted 386BSD systems with SMC >WD8003EP adapters yields errors like: > >cp: ./inetd: No such file or directory > >and though most files copy okay, the files for which an error is >reported get truncated. Worse, when using cpio -p, truncation occurs, >but no errors are reported! It was suggested mounting with smaller r/wsize(=4096 solves the problem for me). For one person, r/wsize=2048 was necessary with a WD8013. It was also recommended that a NFS only be read from, not written to. I guess with idea being that you don't not know conditions at the other end. In the case of my small network (2 PC's) writing is not a problem. The following allows cp/cpio without errors: # mount -t nfs -o rw,rsize=4096,wsize=4096 worm:/ /worm # mount -t nfs -o rw,rsize=4096,wsize=4096 worm:/usr /worm/usr or in fstab: worm:/ /worm nfs rw,rsize=4096,wsize=4096 0 0 worm:/usr /worm/usr nfs rw,rsize=4096,wsize=4096 0 0 Thanks everyone! -Andrew Moore <alm@netcom.com>