From owner-freebsd-current@FreeBSD.ORG Wed Sep 1 21:42:27 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 810D116A4CE for ; Wed, 1 Sep 2004 21:42:27 +0000 (GMT) Received: from ganymede.hub.org (blk-222-46-91.eastlink.ca [24.222.46.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E5F843D46 for ; Wed, 1 Sep 2004 21:42:27 +0000 (GMT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 53CAD375FD; Wed, 1 Sep 2004 18:42:27 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 4CCF6374CD; Wed, 1 Sep 2004 18:42:27 -0300 (ADT) Date: Wed, 1 Sep 2004 18:42:27 -0300 (ADT) From: "Marc G. Fournier" To: Allan Fields In-Reply-To: <20040901200257.GA92717@afields.ca> Message-ID: <20040901184050.J47186@ganymede.hub.org> References: <20040901151405.G47186@ganymede.hub.org> <20040901200257.GA92717@afields.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 21:42:27 -0000 On Wed, 1 Sep 2004, Allan Fields wrote: > 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. Understood, and agreed ... *but* ... is there a way, before I do that, of determining if this is something that needs to be fixed at the OS level? Is there a leak here that I can somehow identify while its in this state? The server has *only* been up 25 days ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664