From owner-freebsd-hackers Wed Sep 3 20:41:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA00714 for hackers-outgoing; Wed, 3 Sep 1997 20:41:01 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA00708 for ; Wed, 3 Sep 1997 20:40:57 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id WAA01942; Wed, 3 Sep 1997 22:40:51 -0500 (EST) From: "John S. Dyson" Message-Id: <199709040340.WAA01942@dyson.iquest.net> Subject: Re: 2.2-stable swap usage? In-Reply-To: <19970903223343.28431@pobox.com> from Brian Campbell at "Sep 3, 97 10:33:43 pm" To: brianc@pobox.com (Brian Campbell) Date: Wed, 3 Sep 1997 22:40:51 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brian Campbell said: > On Wed, Sep 03, 1997 at 09:19:05PM -0500, John S. Dyson wrote: > > Brian Campbell said: > > > Is it normal for 24M of swap to be marked in-use when nothing appears to be using it? > > > System has 64M RAM, and has been up and running AccelX for about a week. > > > Killing syslogd and cron didn't help. There wasn't much left ... > > > > All of the address ranges marked by swap in the /proc/*/map can be in > > swap space. Looks like there is enough of 'em. Unmount the mfs, and > > I would suspect alot of your space will be freed up... > > I suppose I should've included a 'df' of /tmp. There was less than 50k in use at that point. > Next time it happens, I'll try to umount the mfs and see if it changes anything ... > Once the pages in MFS or any other process are paged out, those pages will be persistant in swap until the process exits (or the memory is explicitly deallocated by the process.) MFS doesn't deallocate any of it's memory usage. -- John dyson@freebsd.org jdyson@nc.com