Date: Wed, 8 Apr 2009 18:13:36 -0400 From: Ryan Stone <rysto32@gmail.com> To: current@freebsd.org Subject: NFS lockd/statd lock up network connection Message-ID: <bc2d970904081513l694a8a09x3d24f407ab9499d3@mail.gmail.com> In-Reply-To: <bc2d970904081512l66fd6da9xba84886cd49bab40@mail.gmail.com> References: <49D851FC.4090103@sdf.lonestar.org> <bc2d970904081505m7ae99eaft75bdd908ba2f4b49@mail.gmail.com> <bc2d970904081512l66fd6da9xba84886cd49bab40@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Forgot to reply all, sorry. ---------- Forwarded message ---------- From: Ryan Stone <rysto32@gmail.com> Date: Wed, Apr 8, 2009 at 6:12 PM Subject: Re: NFS lockd/statd lock up network connection To: Tom McLaughlin <tmclaugh@sdf.lonestar.org> On Wed, Apr 8, 2009 at 6:05 PM, Ryan Stone <rysto32@gmail.com> wrote: > > em0: Could not setup receive structures > > The em driver prints this out when it can't allocate mbufs or clusters. > Can you show the output of vmstat -z? This error is indicative of a leak of > mbufs or clusters, or a misconfiguration(too few mbufs or clusters). > > Ryan Stone > Also, can you run sysctl dev.em.0.debug=1? That will print a bunch of debugging information to the console. The two lines I'm most interested in are Std mbuf failed = <value> Std mbuf cluster failed = <value>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bc2d970904081513l694a8a09x3d24f407ab9499d3>