From owner-freebsd-bugs@FreeBSD.ORG Sun Oct 18 01:20:01 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B71881065676 for ; Sun, 18 Oct 2009 01:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 94B838FC20 for ; Sun, 18 Oct 2009 01:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9I1K1RU043298 for ; Sun, 18 Oct 2009 01:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9I1K1aW043297; Sun, 18 Oct 2009 01:20:01 GMT (envelope-from gnats) Resent-Date: Sun, 18 Oct 2009 01:20:01 GMT Resent-Message-Id: <200910180120.n9I1K1aW043297@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, kickbsd Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 965D4106566C for ; Sun, 18 Oct 2009 01:14:55 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 85D238FC0A for ; Sun, 18 Oct 2009 01:14:55 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n9I1EsAU045436 for ; Sun, 18 Oct 2009 01:14:54 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n9I1Es21045435; Sun, 18 Oct 2009 01:14:54 GMT (envelope-from nobody) Message-Id: <200910180114.n9I1Es21045435@www.freebsd.org> Date: Sun, 18 Oct 2009 01:14:54 GMT From: kickbsd To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/139715: vfs.numvnodes leak on bussy zfs X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Oct 2009 01:20:01 -0000 >Number: 139715 >Category: kern >Synopsis: vfs.numvnodes leak on bussy zfs >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Oct 18 01:20:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: kickbsd >Release: 8.0-RC1 >Organization: none >Environment: FreeBSD lab-backup012.local 8.0-RC1 FreeBSD 8.0-RC1 #3: Tue Oct 13 08:44:45 UTC 2009 root@lab-backup012.local:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I have a reproducible hangs on busy zfs file system. Just run rsync to zfs server from other data source. vfs.numvnodes tends to leak and when reach kern.maxvnodes no new files can be created or modified. There is no kernel panic and already existing shell sessions works but system can not rebutted safely after vfs.numvnodes reached kern.maxvnodes. After rsync complated vfs.numvnodes never goes back to normal. I have increased kern.maxvnodes to kern.maxvnodes: 1.800.000 but vfs.numvnodes slowly grows for about 10.000 vnodes per 4 hours rsync session. Same behavior observed with relatively bussy server with ~1k rrd databases which updated every 5 min. >How-To-Repeat: Run long rsync session to zfs filesystem or run update on 1k+ rrd databases. >Fix: N/A >Release-Note: >Audit-Trail: >Unformatted: