From owner-freebsd-stable@FreeBSD.ORG Tue Mar 9 00:12:20 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A29616A4CE for ; Tue, 9 Mar 2004 00:12:20 -0800 (PST) Received: from spam2.snu.ac.kr (spam2.snu.ac.kr [147.46.10.68]) by mx1.FreeBSD.org (Postfix) with SMTP id 6653E43D2D for ; Tue, 9 Mar 2004 00:12:19 -0800 (PST) (envelope-from nospam@users.sourceforge.net) Received: (snipe 14759 invoked by alias); 9 Mar 2004 08:12:13 +0900(KST) Received: from nospam@users.sourceforge.net with SpamSniper2.76 (Processed in 0.043218 secs); Received: from unknown (HELO sis1.snu.ac.kr) (147.46.10.36) by 0 with SMTP; 9 Mar 2004 08:12:13 +0900(KST) X-RCPTTO: freebsd-stable@freebsd.org, Received: from users.sourceforge.net (cisr.snu.ac.kr [147.46.44.181]) by sis1.snu.ac.kr (8.12.10/8.12.10) with ESMTP id i2988eUs320432 for ; Tue, 9 Mar 2004 17:08:40 +0900 Message-ID: <404D7C5B.9040104@users.sourceforge.net> Date: Tue, 09 Mar 2004 17:12:11 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040207 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <404D6D41.3040508@users.sourceforge.net> <20040309080145.GA35678@walton.maths.tcd.ie> In-Reply-To: <20040309080145.GA35678@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: vnode_pager_putpages hanged my machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 08:12:20 -0000 David Malone wrote: > On Tue, Mar 09, 2004 at 04:07:45PM +0900, Rob wrote: > >>Did the machine end up in an eternal loop and ate up all resources? >>A bug in vnode? Or in the pager? > > It looks like convert was killed because it ran your machine out > of memory - that might explain extream slugishness if everything > else had been swapped out. It also looks like /var was completly > full. Yes, I agree. But any regular user can bring the system virtually to a stand still this way. Shouldn't the OS prevent this to happen? That's why I suspect a bug somewhere allowing this to happen. Regards, Rob.