Subject: NFS fragile?
To: None <port-i386@NetBSD.ORG>
From: Simon J. Gerraty <sjg@quick.com.au>
List: port-i386
Date: 07/12/1997 23:07:23
I just hung my 1.2G box... by writing too quick to an NFS server.

Client is P166 running the recent 1.2G snapshot, with 3C509 nic.
Server is i486/DX33 running a 1.2F kernel (Jun08) and a WD8003 8bit
NIC.

[Hey I know, the P166 is to replace the 486 :-)]

The nfs filesys is mounted with no special options, and all I did was:

mv /tmp/foo/* /server/tmp/foo

foo/* is a total of about 60K.  Only about 8k made it before I got:

Jul 12 22:49:40 zen /netbsd: ed0: warning - receiver ring buffer overrun
Jul 12 22:49:40 zen /netbsd: ed0: warning - receiver ring buffer overrun
Jul 12 22:50:20 zen last message repeated 3 times
:
:

on the server and the client locked up.  Or at least its filesystem
did.  tcpdump shows the P166 responding to ping, and the xterms still
respond to the X server, but I've only seen one nfs packet in several
minutes and all shells are wedged.

Obviously the P166 is able to write to the net faster than the 486
with its 8bit WD8003 can read, but this seems a bit fragile.

I'll remount with write size set at 1k... after I reboot.

--sjg