Often experiencing nfs server foo:/bar: not responding

[Mohan Srinivasan]

Still investigating. From what we can tell (in Steve Kargl's case), this
looks like a FreeBSD NFS server issue. The nfsd's on his server are all
blocked in uma_zone_slab (no response to NFS requests, NFS clients keep 
rexmitting). Don't have core, so don't know more.

I'll take a look at the core once he sends it to me. Hopefully we'll have
a fix for this soon.

--- David O'Brien <obrien at freebsd.org> 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?
> 
> -- 
> -- 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?
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>