Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 08 May 2013 09:17:13 +0200
From:      =?UTF-8?Q?G=C3=B6ran_L=C3=B6wkrantz?= <goran.lowkrantz@ismobile.com>
To:        Mikolaj Golub <trociny@FreeBSD.org>
Cc:        Kostik Belousov <kib@FreeBSD.org>, freebsd-stable@freebsd.org
Subject:   Re: Nullfs leaks i-nodes
Message-ID:  <DEF445892B6F7F6447517A54@[172.16.2.45]>
In-Reply-To: <20130507204149.GA3267@gmail.com>
References:  <B799E3B928B18B9E6C68F912@[172.16.2.62]> <20130507204149.GA3267@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--On May 7, 2013 23:41:51 +0300 Mikolaj Golub <trociny@FreeBSD.org> 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







Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DEF445892B6F7F6447517A54>