From owner-freebsd-current@FreeBSD.ORG Mon Apr 21 18:09:11 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 A19E337B401; Mon, 21 Apr 2003 18:09:11 -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 95CC343FD7; Mon, 21 Apr 2003 18:09:10 -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 93BD710A; Mon, 21 Apr 2003 18:09:09 -0700 (PDT) From: "Lucky Green" To: Date: Mon, 21 Apr 2003 18:09:04 -0700 Message-ID: <007a01c3086b$c4a81ae0$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 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: dillon@apollo.backplane.com Subject: 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: Tue, 22 Apr 2003 01:09:11 -0000 Matt Dillon wrote: :> I suggest changing this: :> :> if ((vm_swap_size < 64 && vm_page_count_min()) || :> (swap_pager_full && vm_paging_target() > 0)) { :> :> To this: :> :> if (pass != 0 && :> ((vm_swap_size < 64 && vm_page_count_min()) || :> (swap_pager_full && vm_paging_target() > 0))) { Matt, You patch, at least so far, appears to prevent processes from being killed due to lack of memory. Thanks! However, I am still seeing other memory-related error messages in the syslog: ---------- Apr 20 22:54:32 pakastelohi kernel: swap_pager_getswapspace: failed Apr 22 00:34:29 pakastelohi kernel: ENOMEM 0xc6bb8c00 on 0xc6d91380(ad4s1.bde) Apr 22 00:34:34 pakastelohi kernel: ENOMEM 0xc6bc5300 on 0xc6d91380(ad4s1.bde) Apr 22 00:48:49 pakastelohi kernel: ENOMEM 0xc65b8e00 on 0xc6d91380(ad4s1.bde) Apr 22 00:52:51 pakastelohi kernel: ENOMEM 0xc6477000 on 0xc6d91380(ad4s1.bde) Apr 22 00:52:51 pakastelohi kernel: ENOMEM 0xc860fc00 on 0xc6d91380(ad4s1.bde) Apr 22 01:07:14 pakastelohi kernel: ENOMEM 0xc69b4900 on 0xc6865880(ad6s1c.bde) Apr 22 01:07:14 pakastelohi kernel: ENOMEM 0xc85fee00 on 0xc6865880(ad6s1c.bde) ----------- I had reported the "swap_pager_getswapspace: failed" and GBDE "ENOMEM" errors in earlier, separate threads. The "swap_pager_getswapspace: failed" occurred most likely, though I am not positive, during the copying of a large file between two unencrypted partitions. The GBDE "ENOMEM" errors occurred while moving multiple GBs in directories containing files of various sizes, from a few MB to about 800MB, from one GBDE partition to another. (gbde.c,v 1.13) What I don't know is what the impact of these messages is: can they be safely ignored or are they indicative of processes failing to execute as requested and/or possible data corruption taking place? Thanks, --Lucky