From owner-freebsd-current@FreeBSD.ORG Wed Sep 1 20:02:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77FA316A4CE for ; Wed, 1 Sep 2004 20:02:58 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 484F343D3F for ; Wed, 1 Sep 2004 20:02:58 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id i81K2v4o093639; Wed, 1 Sep 2004 16:02:57 -0400 (EDT) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id i81K2vgh093638; Wed, 1 Sep 2004 16:02:57 -0400 (EDT) (envelope-from afields) Date: Wed, 1 Sep 2004 16:02:57 -0400 From: Allan Fields To: "Marc G. Fournier" Message-ID: <20040901200257.GA92717@afields.ca> References: <20040901151405.G47186@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040901151405.G47186@ganymede.hub.org> User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: vnode leak in FFS code ... ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2004 20:02:58 -0000 On Wed, Sep 01, 2004 at 03:19:27PM -0300, Marc G. Fournier wrote: > I don't know if this is applicable to -current as well, but so far, > anything like this I've uncovered in 4.x has needed an equivalent fix in > 5.x, so figured it can't hurt to ask, especially with everyone working > towards a STABLE 5.x branch ... I do not have a 5.x machine running this > sort of load at the moment, so can't test, or provide feedback there ... > all my 5.x machines are more or less desktops ... > > On Saturday, I'm going to try an unmount of the bigger file system, to see > if it frees everything up without a reboot ... but if someone can suggest > something to check to see if it is a) a leak and b) is fixable between now > and then, please let me know ... again, this is a 4.10 system, but most of > the work that Tor and David have done (re: vnodes) in the past relating to > my servers have been applied to 5.x first, and MFC'd afterwards, so I > suspect that this too many be something that applies to both branches ... Unmounting the filesystems will call vflush() and should flush all vnodes from under that mount point. I'm not entirely sure if this is the best you can do w/o rebooting. -- Allan Fields, AFRSL - http://afields.ca 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541