Date: Wed, 20 Jun 2007 15:28:31 -0400
From: John Nielsen <lists@jnielsen.net>
To: freebsd-current@freebsd.org
Cc: Dan Mack <mack@macktronics.com>
Subject: Re: ZFS and deadlock with {nullfs,NFS}
Message-ID: <200706201528.31349.lists@jnielsen.net>
In-Reply-To: <20070620111405.K71264@coco.macktronics.com>
References: <1182354823.6504.23.camel@shumai.marcuscom.com> <20070620160306.GA74674@rot26.obsecurity.org> <20070620111405.K71264@coco.macktronics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 20 June 2007 12:30:23 pm Dan Mack wrote: > On Wed, 20 Jun 2007, Kris Kennaway wrote: > > <snip> > > > 404 at the moment, but look for processes involving zil* in the > > backtrace. I had to disable zil (vfs.zfs.zil_disable=1 tunable) to > > prevent low-memory deadlocks on my machines. Since then it's been > > fine. > > > > You may also wish to use my patches (see the archives) to improve > > performance and low-memory behaviour. > > > > Kris > > Does someone have these recommended sysctls embodied in an example > /boot/loader.conf yet? Here is mine, does it look reasonable to keep ZFS > from running into the kmem_ memory panics? I have no idea if I found all > of your recommendations so it would be nice if they were summarized in one > place. > > | # /boot/loader.conf i386 / 1GB memory / SMP > | kern.maxvnodes="50000" Note that kern.maxvnodes has to be set in /etc/sysctl.conf to have any effect. JN
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200706201528.31349.lists>