From owner-freebsd-pf@FreeBSD.ORG Thu Nov 27 10:34:25 2014 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5737181 for ; Thu, 27 Nov 2014 10:34:25 +0000 (UTC) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id 8FE0AD66 for ; Thu, 27 Nov 2014 10:34:25 +0000 (UTC) Received: from [10.0.1.2] (static-71-177-216-148.lsanca.fios.verizon.net [71.177.216.148]) (authenticated bits=0) by zoom.lafn.org (8.14.7/8.14.7) with ESMTP id sARA9tKl031943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 27 Nov 2014 02:09:56 -0800 (PST) (envelope-from bc979@lafn.org) From: Doug Hardie Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Swap Issue Message-Id: <4009E30B-FC0C-4BE0-A318-CD2ED5E28281@lafn.org> Date: Thu, 27 Nov 2014 02:09:55 -0800 To: "freebsd-pf@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2014 10:34:25 -0000 I have a most interesting situation that just manifested itself this = morning in a way I could begin to diagnose. The system runs 8.2-P3 and = has no users, just one process that runs 24x7. Its been running since = 8.2 was first released. Every now and then the process becomes = non-responsive. Today it managed to spit out an error that the system = had run out of swap space before it hung. This is quite interesting in that there are 5.5GB of free memory. The = only time that changes is at 3 am when the various periodic processes = run. However, I don=E2=80=99t suspect those as I have numerous other = systems that have considerably less memory and higher usage that do not = experience this issue. I have increased the swap space to prevent this = issue, but something must be going bonkers to cause the swap space to = get used. Usually there are only 15MB used. Every time the system = notifies me that it has the problem, by the time I can look at it, swap = is back to normal. I have never been able to catch the system with more = than 15 MB used. Is there any way after the fact to figure out what was = using the swap? I suspect not, but thought I=E2=80=99d ask just in case = I have overlooked something.