From owner-freebsd-stable@freebsd.org Wed Jun 8 22:02:36 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 568BAB70A8B for ; Wed, 8 Jun 2016 22:02:36 +0000 (UTC) (envelope-from mi+oro@aldan.algebra.com) Received: from vms173023pub.verizon.net (vms173023pub.verizon.net [206.46.173.23]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CCC91B33 for ; Wed, 8 Jun 2016 22:02:35 +0000 (UTC) (envelope-from mi+oro@aldan.algebra.com) Received: from vz-proxy-l005.mx.aol.com ([64.236.82.152]) by vms173023.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0O8H00JQ613IRQ80@vms173023.mailsrvcs.net> for freebsd-stable@FreeBSD.org; Wed, 08 Jun 2016 16:02:11 -0500 (CDT) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=WpDWSorv c=1 sm=1 tr=0 a=a3t/a0oOYlYu/nGe1mf8ZA==:117 a=pD_ry4oyNxEA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=TWVjGQL9O7it2J5u1S4A:9 a=QEXdDO2ut3YA:10 a=2z9rS1_vppYsJW5t73gA:9 a=2oDY5yJidKnIb6dh:21 a=_W_S_7VecoQA:10 Received: by 100.1.241.90 with SMTP id 7bfd0cea; Wed, 08 Jun 2016 21:02:11 GMT To: freebsd-stable@FreeBSD.org From: "Mikhail T." Subject: Nasty state after running out of swap Message-id: <057d6b66-8051-213f-e716-efada3692bc0@aldan.algebra.com> Date: Wed, 08 Jun 2016 17:02:09 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2016 22:02:36 -0000 In my absence my desktop managed to run out of memory and had to kill a number of processes: pid 47493 (firefox), uid 105, was killed: out of swap space pid 1665 (thunderbird), uid 105, was killed: out of swap space pid 975 (kdeinit4), uid 105, was killed: out of swap space pid 1344 (mysqld), uid 105, was killed: out of swap space pid 898 (Xorg), uid 0, was killed: out of swap space pid 1430 (pidgin), uid 105, was killed: out of swap space While that's unfortunate in its own right, the current state of the machine is just weird... After the massacre the swap-usage is down to 5% and memory is plentiful. top(1) reports: last pid: 85719; load averages: 0.17, 0.15, 0.11 up 25+21:17:34 16:50:27 123 processes: 1 running, 102 sleeping, 11 stopped, 8 zombie, 1 waiting CPU: 0.1% user, 0.0% nice, 1.8% system, 0.3% interrupt, 97.7% idle Mem: 17M Active, 7276K Inact, 9876M Wired, 10M Cache, 1032M Buf, 28M Free ARC: 1114M Total, 264M MFU, 282M MRU, 69K Anon, 44M Header, 524M Other Swap: 12G Total, 616M Used, 11G Free, 5% Inuse And yet, various commands hang for a while in either pfault or zombie state upon completion. For example, top, when I tried to exit it, hung for about a minute with Ctrl-T reporting: load: 0.13 cmd: top 85718 [pfault] 19.04r 0.00u 0.01s 0% 2532k Why would a machine with so much free memory continue to act this way? Is it yet to recover from the "out of swap" situation? I'm sure, a reboot will fix everything, but I expected FreeBSD to be better than that... Running 10.3-stable from April 18 here. Thanks! -mi