Date: Sun, 4 Apr 1999 11:36:36 -0500 (EST) From: Alfred Perlstein <bright@rush.net> To: Murata Shuuichirou <mrt@notwork.org> Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>, current@FreeBSD.ORG, wpaul@ctr.columbia.edu Subject: Re: More on rl0 woes Message-ID: <Pine.BSF.3.96.990404113125.4169W-100000@cygnus.rush.net> In-Reply-To: <87soagd15f.fsf@kotonoha.s.notwork.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 Apr 1999, Murata Shuuichirou wrote: > In message <199904040913.RAA26683@ariadne.tensor.pgs.com>, > `shocking@prth.pgs.com' wrote: > > On the offchance that mty problems were chipset related, I swapped the > > RealTek with the de0 card in my other machine, a 233MHz k6. It being a > > socket 7 mboard presumably has a later PCI bios. Still the same symptoms - > > hangs on NFS access. These can be interrupted and other network traffic > > continues fine. To reproduce, take your RealTek equipped machine and place a > > copy of /usr/src on it. Export /usr/src so that it can be NFS mounted by > > other machines. From the other machines, do an ls -CFR of /usr/src. It will > > hang partway through. > > I have probably same problem here. NFS hangs and other > network traffic is still alive. Though, my situation > differs a little from yours. I have two RealTek NFS clients > and NFS server has another chip. Both of RealTek NFS clients > (Celeron 300MHz and MediaGX 266MHz) have the problem. > > To reproduce: > Install bytebench on the RealTek machine. > Set env var TMPDIR to somewhere NFS mounted dir. > Do "bytebench fstime". I have a solution and a workaround for you guys, solution: ditch the cheap PoS cards and get an fxp or xl card workaround: switch from UDP to TCP mounts or TCP to UDP, make sure the packet size used for the NFS mounts is a small value, try NFSv3, or if you are already using NFSv3, try NFSv2. Yes, the workaround seems like "just try several permutations", but I experianced the same problems, tweaking my NFS mounts, especially to use smaller read/write values made the problem go away. I think that switching to TCP may help. When i got some decent network hardware, my problems went away. -Alfred > > -- > Murata Shuuichirou > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Alfred Perlstein - Admin, coder, and admirer of all things BSD. -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990404113125.4169W-100000>