From owner-freebsd-current@FreeBSD.ORG Sat Apr 19 07:45:28 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 09CD337B401 for ; Sat, 19 Apr 2003 07:45:28 -0700 (PDT) Received: from noisebox.cypherpunks.to (adsl-208-201-229-163.sonic.net [208.201.229.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AC3543F3F for ; Sat, 19 Apr 2003 07:45:25 -0700 (PDT) (envelope-from shamrock@cypherpunks.to) Received: from VAIO650 (adsl-208-201-229-160.sonic.net [208.201.229.160]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by noisebox.cypherpunks.to (Postfix) with ESMTP id C6B8510D for ; Sat, 19 Apr 2003 07:45:23 -0700 (PDT) From: "Lucky Green" To: Date: Sat, 19 Apr 2003 07:45:21 -0700 Message-ID: <000501c30682$4e5e64b0$6601a8c0@VAIO650> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Subject: 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: Sat, 19 Apr 2003 14:45:28 -0000 There appears to be a memory management bug that affects systems without swap files. Processes are killed off due to the server being "out of swap space" even though top shows some 800MB of "inactive" memory available. Apr 18 18:13:25 pakastelohi kernel: swap_pager_getswapspace: failed Apr 18 21:10:04 pakastelohi kernel: pid 15680 (smtpd), uid 1045, was killed: out of swap space Apr 18 23:14:47 pakastelohi kernel: pid 17730 (smtpd), uid 1045, was killed: out of swap space Configuration: Dual PIII-800, 1GB of RAM swapfile="NO" is set in rc.conf CURRENT from April 18 I suspect that for some reason memory listed as "inactive" by top is not being correctly allocated to new processes when no swapfile is available, since the errors do not appear until memory listed as "free" has dropped to about 1.5-3k. Let me know if you need additional information. --Lucky