From owner-freebsd-current@FreeBSD.ORG Wed Apr 23 06:57:08 2003 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 C32EE37B401 for ; Wed, 23 Apr 2003 06:57:08 -0700 (PDT) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 319F643FCB for ; Wed, 23 Apr 2003 06:57:08 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.9/8.12.5) with ESMTP id h3NDuxjC013387; Wed, 23 Apr 2003 06:56:59 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.9/8.12.5/Submit) id h3NDutIU013386; Wed, 23 Apr 2003 06:56:55 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Wed, 23 Apr 2003 06:56:55 -0700 From: David Schultz To: Lucky Green Message-ID: <20030423135655.GA13246@HAL9000.homeunix.com> Mail-Followup-To: Lucky Green , freebsd-current@freebsd.org, 'Matthew Dillon' References: <200304220345.h3M3jFBu099430@apollo.backplane.com> <00e101c30936$94da3c00$6601a8c0@VAIO650> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00e101c30936$94da3c00$6601a8c0@VAIO650> cc: 'Matthew Dillon' cc: freebsd-current@FreeBSD.ORG Subject: Re: RE: Broken memory management on system with no swap 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, 23 Apr 2003 13:57:09 -0000 On Tue, Apr 22, 2003, Lucky Green wrote: > Matthew Dillon wrote: > > I can't help you with gbde. Looking at the mail > archives[...Thanks, I missed that post] > > What about the "swap_pager_getswapspace: failed" error that still shows > up in the logs? Can it be safely ignored? Yes, you can ignore those messages. Note that although the VM system behaves more reasonably with Matt's patches, bad things can happen when you're out of both memory and swap. GEOM happens to be fairly graceful about it; it waits and retries. But at the same time, you might be losing network packets, for instance. I'm not sure what exactly is causing your system to run out of memory, though. I can copy multi-gigabyte files across unencrypted partitions on a machine with no swap without issue. Perhaps someone else has some ideas...