Date: Mon, 5 Oct 2009 17:49:42 +0200 From: Alex de Kruijff <samesame@akruijff.dds.nl> To: pav@FreeBSD.org Cc: freebsd-ports-bugs@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: ports/138596: [MAINTAINER] sysutils/samesame vlruwk problem Message-ID: <20091005154942.GA1476@Alex1.lan> In-Reply-To: <200909202006.n8KK6AU6091481@freefall.freebsd.org> References: <200909202006.n8KK6AU6091481@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This might be one of those bug reports where your anwser might be: sorry not a bug but a feature. I've run the app and the whole computer seem to freeze. I've rebooted a couple times. Before I filed the PR, I've googled on vlruwk and it seemed like this state indicated a big problem on the OS part. Since then I have come to understand this better. What happens is that the vnodes are running out, and FreeBSD responed to that by waiting a couple seconds becore executing a anything. Thus it becomes unresponcive. I think the ideal solution would be if the OS would slow down the app that is using a (very) large percentage of available vnodes, if it causes the computer to run out of available vnodes. I've also learned that the problem goes away if the value kern.maxvnodes is raised by the administrator, but in my case this needed to add at least 200%. # sysctl kern.maxvnodes = <kern.maxvnodes> + 10 000 I've run the app as root. And having root privileges this was easy for me to do, once I knew how to respond to this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091005154942.GA1476>