Many processes stuck in zfs

[Kevin Oberman]

Sigh. My brain is fried. I replied to the wrong thread. Pleas ignore this.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751

> Date: Tue, 09 Mar 2010 16:18:25 -0800
> From: "Kevin Oberman" <oberman at es.net>
> Sender: owner-freebsd-stable at freebsd.org
> 
> > Date: Tue, 9 Mar 2010 21:53:55 +1100
> > From: Peter Jeremy <peterjeremy at acm.org>
> > Sender: owner-freebsd-stable at freebsd.org
> > 
> > On 2010-Mar-09 10:15:53 +0100, Stefan Bethke <stb at lassitu.de> wrote:
> > >Over the past couple of months, I've more or less regularly observed machines having more and more processes stuck in the zfs wchan.  The processes never recover from that,
> > 
> > How long have you waited?
> > 
> > There seems to be a problem with low free memory handling that causes ZFS
> > to turn into cold molasses.  The work-around is to run a program that
> > allocates a decent size chunk of memory and then exits.  The original
> > suggestion was something like:
> > 	perl -e '@x = (0) x 1000000;'
> > I've written a short program that allocates and dirties ~100MB and then
> > exits and run it from cron.
> 
> Sigh! I found it. I build my systems without NIS and I had the stock
> nsswitch.conf file. Fixed.
> 
> /me banging my head against the desk.
> 
> Thanks!
> -- 
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: oberman at es.net			Phone: +1 510 486-8634
> Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>