From owner-freebsd-stable@FreeBSD.ORG Wed May 8 07:17:19 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4EDA6273; Wed, 8 May 2013 07:17:19 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (mail.ismobile.com [IPv6:2a00:f680:101:11::4]) by mx1.freebsd.org (Postfix) with ESMTP id 0573EA5A; Wed, 8 May 2013 07:17:19 +0000 (UTC) Received: from mail.ismobile.com (localhost [127.0.0.1]) by dkim.mail.ismobile.com (Postfix) with ESMTP id B8D352B5578; Wed, 8 May 2013 07:17:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ismobile.com; h=date:from :to:cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=selector1; bh=CaMk/5G al0wrRnaiP2j+7NWp5bQ=; b=GtGjrT8kG1R65NPL/HvcKV6BnOwg9HyAyNcefRW glYsrGUZQbvRfqgmRILGp1wS08o/bM6kRitNU2OulTfHFATv2W9BUHXfT1hjd3fU GdO2MYkisyTivOV5EEJ8DZC7+X57yNV4vKciPnMZdVkjQPuk1WZFVEzJPBrZndhR 1wow= DomainKey-Signature: a=rsa-sha1; c=nofws; d=ismobile.com; h=date:from:to :cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=selector1; b=o 6hDO67lbvo5ODmDdv8LG5XMznSljxS/h6U+mKlfHxHPZDmy5k77gxQc17blX6/o+ Hl9p/LSB0BqyYE6rATJG2I0FOBbLP7yhuhLv+rJAaySG6sgnCaFTSTzE8xIN5GSp s6V3P3U9YIAopoM+nAMh/sdsrP8qYdU35diKagnQjw= Received: from [172.16.2.45] (glz-macbookpro.hq.ismobile.com [172.16.2.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTPSA id E95BE2B548E; Wed, 8 May 2013 07:17:14 +0000 (UTC) Date: Wed, 08 May 2013 09:17:13 +0200 From: =?UTF-8?Q?G=C3=B6ran_L=C3=B6wkrantz?= To: Mikolaj Golub Subject: Re: Nullfs leaks i-nodes Message-ID: In-Reply-To: <20130507204149.GA3267@gmail.com> References: <20130507204149.GA3267@gmail.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Kostik Belousov , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 08 May 2013 07:17:19 -0000 --On May 7, 2013 23:41:51 +0300 Mikolaj Golub wrote: > On Tue, May 07, 2013 at 08:30:06AM +0200, G=C3=B6ran L=C3=B6wkrantz = wrote: >> I created a PR, kern/178238, on this but would like to know if anyone >> has any ideas or patches? >> >> Have updated the system where I see this to FreeBSD 9.1-STABLE #0 >> r250229 and still have the problem. > > I am observing an effect that might look like inode leak, which I > think is due free nullfs vnodes caching, recently added by kib > (r240285): free inode number does not increase after unlink; but if I > purge the free vnodes cache (temporary setting vfs.wantfreevnodes to 0 > and observing vfs.freevnodes decreasing to 0) the inode number grows > back. > > You have only about 1000 inodes available on your underlying fs, while > vfs.wantfreevnodes I think is much higher, resulting in running out of > i-nodes. > > If it is really your case you can disable caching, mounting nullfs > with nocache (it looks like caching is not important in your case). > > -- > Mikolaj Golub Thanks Mikolaj, mounting the active fs with 'nocache' fixed it, keeping=20 ifree steady. Any idea how to "fix" this in NanoBSD? The data partition is created with=20 only 1024 i-nodes in the script, so any use that includes file deletion on=20 this r/w area will be bitten. As the nocache attribute is not valid for device mounts, I see no way to=20 inherit it to the nullfs mounts for this specific partition. Easiest thing could be to set vfs.wantfreevnodes=3D0 in the default=20 sysctl.conf, maybe? But will this have implications for non-nullfs=20 filesystems? Only UFS? Even ZFS? Thanks again, G=C3=B6ran