From owner-freebsd-questions Sat May 22 20:23:40 1999 Delivered-To: freebsd-questions@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 2226B14F95 for ; Sat, 22 May 1999 20:23:37 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id UAA04443; Sat, 22 May 1999 20:21:35 -0700 (PDT) Message-Id: <199905230321.UAA04443@implode.root.com> To: Doug White Cc: Stuart Henderson , freebsd-questions@FreeBSD.ORG Subject: Re: vmopar In-reply-to: Your message of "Sat, 22 May 1999 18:48:46 PDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 22 May 1999 20:21:35 -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Fri, 21 May 1999, Stuart Henderson wrote: > >> Hi, I have a process that can't be killed which top shows in >> state vmopar. The process is a web server (zeus) running from >> nfs mounted files. This is under 3.1-release. Can anyone >> suggest what vmopar means? (these files will be moved away >> from nfs soon which I guess will avoid this situation, but >> I'd still like to know why :) > >The files it gets stuck on aren't being changed, are they? Mat Dillion is >tracking down a deadlock condition in -current that sticks up in vmopar. > >vmopar - VM Operation, I'm guessing. VM object page remove. It's a wait condition that occurs when a page is marked "busy", but the kernel wants to remove (free) the page from the VM object. Usually caused by a missing page unbusy somewhere, but can also be caused by other things (like wedged hardware). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message