From owner-freebsd-stable@FreeBSD.ORG  Tue May  7 20:41:56 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 4BEFB80A;
 Tue,  7 May 2013 20:41:56 +0000 (UTC)
 (envelope-from to.my.trociny@gmail.com)
Received: from mail-ea0-x22e.google.com (mail-ea0-x22e.google.com
 [IPv6:2a00:1450:4013:c01::22e])
 by mx1.freebsd.org (Postfix) with ESMTP id B01B8DE;
 Tue,  7 May 2013 20:41:55 +0000 (UTC)
Received: by mail-ea0-f174.google.com with SMTP id f15so560466eak.33
 for <multiple recipients>; Tue, 07 May 2013 13:41:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=x-received:sender:date:from:to:cc:subject:message-id:references
 :mime-version:content-type:content-disposition
 :content-transfer-encoding:in-reply-to:user-agent;
 bh=3xiwp2rjIemQfbVaytw0d41LpzbUg2VfgyL11d0C8Ww=;
 b=g+lE6S+uQQsdWSXDf1JFs5Eh3uwpoSzWXbWbMJTW8GbR4Nz+W8uZTPXNIQVy954+5x
 RKlKe0uRJlDvoSVkOvmm+rXKUlyBt6goK/6PB1qAHXjWOMdjldxcwTKYlCcDuvCaUe4G
 Ju1voc722lZPV0Elm4GQRwDl3llvIiWRu+mVljl+KIR/EFmWmuIyXMRyk+7UTYYqBo7l
 RZix3D3cbhG0rBjJMOz5pyFYl0ZlaOkKohZrnsxit2ov+CydWQ9aVvuawDrjo/EoYfP9
 9rI7TTmxgYKJ4GyfApF38BQQE1dReJsq4QX6la29B+hK5SwjHi58scpqbIuM3AsHeq4U
 WvEA==
X-Received: by 10.14.202.201 with SMTP id d49mr9294005eeo.1.1367959314775;
 Tue, 07 May 2013 13:41:54 -0700 (PDT)
Received: from localhost ([178.150.115.244])
 by mx.google.com with ESMTPSA id w43sm35070452eeg.14.2013.05.07.13.41.52
 for <multiple recipients>
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Tue, 07 May 2013 13:41:53 -0700 (PDT)
Sender: Mikolaj Golub <to.my.trociny@gmail.com>
Date: Tue, 7 May 2013 23:41:51 +0300
From: Mikolaj Golub <trociny@FreeBSD.org>
To: =?utf-8?B?R8O2cmFuIEzDtndrcmFudHo=?= <goran.lowkrantz@ismobile.com>
Subject: Re: Nullfs leaks i-nodes
Message-ID: <20130507204149.GA3267@gmail.com>
References: <B799E3B928B18B9E6C68F912@[172.16.2.62]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <B799E3B928B18B9E6C68F912@[172.16.2.62]>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Kostik Belousov <kib@FreeBSD.org>, 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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 20:41:56 -0000

On Tue, May 07, 2013 at 08:30:06AM +0200, Göran Löwkrantz 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