From owner-freebsd-current@FreeBSD.ORG Sun Nov 11 22:48:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C02916A468 for ; Sun, 11 Nov 2007 22:48:01 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 21A7F13C494; Sun, 11 Nov 2007 22:47:57 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4737869B.7020105@FreeBSD.org> Date: Sun, 11 Nov 2007 23:47:55 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: mustkaru References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: RELENG_7: swap_pager_getswapspace(3): failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 11 Nov 2007 22:48:01 -0000 mustkaru wrote: > Hi, > > I updated to RELENG_7 two yesterday, and under usual load started > getting hundreds of messages > > swap_pager_getswapspace(3): failed > > The system swap is 96% full; it is less than 20% usually under the > same load. The system started to kill off processes because of lack of > swap space: > > pid 52606 (thunderbird-bin), uid 1001, was killed: out of swap space > swap_pager_getswapspace(2): failed > pid 13984 (evince), uid 1001, was killed: out of swap space > > I suppose there's no way to get back to the more stable BETA2 ? When > cvsuping, I noticed > > 52815 Nov 8 14:03 vm_page.c > > had been changed. Might it be related to that? Might a next possible > change in that get back a more stable swapper. . .? This means you ran out of swap space because applications were requesting more virtual memory than your system contains. This is an application issue, not a kernel issue. Kris