From owner-freebsd-questions@FreeBSD.ORG Mon Jul 18 04:38:32 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0028716A41C for ; Mon, 18 Jul 2005 04:38:31 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F84A43D45 for ; Mon, 18 Jul 2005 04:38:31 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 01B5BA246A7 for ; Mon, 18 Jul 2005 01:38:29 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75293-09 for ; Mon, 18 Jul 2005 04:38:29 +0000 (GMT) Received: from ganymede.hub.org (blk-224-176-51.eastlink.ca [24.224.176.51]) by hub.org (Postfix) with ESMTP id 92F03A246A5 for ; Mon, 18 Jul 2005 01:38:29 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 16C9C352F0; Mon, 18 Jul 2005 01:38:30 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 118E6340D8 for ; Mon, 18 Jul 2005 01:38:30 -0300 (ADT) Date: Mon, 18 Jul 2005 01:38:30 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-questions@freebsd.org Message-ID: <20050718013156.U1035@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: WARNING: Major vnode leakage in RELENG_4 NFS ... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2005 04:38:32 -0000 Hopefully that caught enough attention :) I've recently been having problems with one of my servers *hanging* that I've just recently traced down to what looks to be a vnode leak in the latest NFS code in the RELENG_4 branch ... Unfortunately, my 'debugging' is at a stand still, but if anyone is noticing issues with their 4.x, where the server seems to hang, take a look at your 'sysctl debug.freevnodes' while doing some operations on an NFS mount ... To "compensate" for the issue on my server, I've changed my scripts so that they umount;mount the NFS file system before doing any major operations, to free up the vnodes, which so far seems to be preventing a reoccurance of the lock up ... As an example, I have a process that starts at 1am that does a find across some NFS mounted directories, and my freevnodes has drop'd by ~130k: Jul 18 01:00:00 mercury root: debug.numvnodes: 460354 - debug.freevnodes: 431364 - debug.vnlru_nowhere: 0 - vlruwt Jul 18 01:12:00 mercury root: debug.numvnodes: 460354 - debug.freevnodes: 355260 - debug.vnlru_nowhere: 0 - vlruwt Jul 18 01:24:00 mercury root: debug.numvnodes: 460354 - debug.freevnodes: 307395 - debug.vnlru_nowhere: 0 - vlruwt Without the umount;mount, they drop farther/faster :( ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664