2.1.71: network wierdness and nfs messages

Andrew Auderieth (andrew@work.serve.com)
Sun, 7 Dec 1997 18:43:32 -0500 (EST)

I just installed 2.1.71 (including the nfs dir.c patch posted by Bill
Hawes) on a machine with an adaptec 2940, and two de500 cards. This
machine is a web server which does some heavy nfs work.

The first pecularity is in the ethernet cards. They've apparently decided
that all outbound traffic is errors (though functionally they're working
just fine):

eth0 Link encap:10Mbps Ethernet HWaddr 00:00:F8:05:CD:FC
inet addr:IP Bcast:206.1.57.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:266812034 errors:265974 dropped:0 overruns:0
TX packets:0 errors:37743316 dropped:152663 overruns:0
Interrupt:11 Base address:0x6000

eth1 Link encap:10Mbps Ethernet HWaddr 00:00:F8:05:AC:3B
inet addr:IP Bcast:206.1.57.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22799138 errors:248626 dropped:0 overruns:0
TX packets:0 errors:179445948 dropped:226393 overruns:0
Interrupt:9 Base address:0x6100

The other oddity is superfluous nfs messages popping up. About once a
minute or so, either:
nfs_lookup: filename ino=## in use, count=2,nlink=2
nfs_detry_delete: filename ino=## in use, count=2,nlink=2

pops up...

(and a few time: "lockd: failed to monitor IP" where IP=address of our nfs
server)

If any of this information is of interest to someone, and you want some
further info about our setup, etc (or want to me to run some tests for
further debugging purposes) just let me know...

-- 
				Andrew Auderieth
				      CEO
			DataRealm Internet Services, LLC


http://www.serve.com/					   info@mail.serve.com