On Tue, Jun 20, 2006 at 03:19:53PM +0100, Brian Candler wrote: > On Mon, Jun 19, 2006 at 08:42:29PM -0700, David O'Brien wrote: > > I am getting these errors all the time now (now being -CURRENT newer than > > Dec'05-Jan'06 time frame). Are there some known issues in UDP or NFS > > serving since then? This is on a virtually zero loaded 100Mbit network. > > Both the NFS server and client are FreeBSD-CURRENT systems. > > > > I can trivially trigger this on all my FreeBSD-CURRENT NFS clients, > > simply by exiting Vim. Did something change sometime in 2006 that would > > affect the default NFS mounts? > > # ping -c100 -s1472 your.nfs.server > > Run this when the machine is idle; and run it while you are exercising > the NFS server. Do you see any packet loss? When experiencing "kernel: nfs server server:/files: not responding", I ran this suggest ping. The results were: --- 192.168.1.1 ping statistics --- 100 packets transmitted, 100 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.389/0.511/0.767/0.062 ms -- -- David (obrien_at_FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon?Received on Tue Jun 20 2006 - 18:25:26 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:57 UTC