From owner-freebsd-stable@FreeBSD.ORG Wed Mar 10 11:55:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8206106564A for ; Wed, 10 Mar 2010 11:55:15 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [212.12.50.234]) by mx1.freebsd.org (Postfix) with ESMTP id B1E338FC0A for ; Wed, 10 Mar 2010 11:55:15 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 55D30523A9; Wed, 10 Mar 2010 11:55:14 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Stefan Bethke In-Reply-To: <20100310113516.GA8848@roberto-al.eurocontrol.fr> Date: Wed, 10 Mar 2010 12:55:12 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <864468D4-DCE9-493B-9280-00E5FAB2A05C@lassitu.de> <20100310113516.GA8848@roberto-al.eurocontrol.fr> To: Ollivier Robert X-Mailer: Apple Mail (2.1077) Cc: freebsd-stable@freebsd.org Subject: Re: Many processes stuck in zfs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2010 11:55:16 -0000 Am 10.03.2010 um 12:35 schrieb Ollivier Robert: > According to Stefan Bethke: >> The situation seems to be triggered by zfs receive'ing snapshots from = the sister machine (both synchronize their active ZFS filesystems to = each other, using zfs send and zfs receive). It appears it's the = receiving causing trouble. >=20 > Have you tuned kern.maxvnodes in /etc/sysctl.conf? >=20 > When I move to this new machine, I forgot to get it much higher than = the default (now I use 200000) and it was locking up pretty soon. Had = not a single lockup now. I haven't, it's at the default of 100000. How would I be able to tell = if that limit is being reached? Right now: $ sysctl kern.maxvnodes vfs.numvnodes vfs.freevnodes kern.maxvnodes: 100000 vfs.numvnodes: 87287 vfs.freevnodes: 24993 and on the sister host: $ sysctl kern.maxvnodes vfs.numvnodes vfs.freevnodes kern.maxvnodes: 100000 vfs.numvnodes: 87681 vfs.freevnodes: 7600 Is there a rule of thumb what maxvnodes should be tuned to? Stefan --=20 Stefan Bethke Fon +49 151 14070811