From owner-freebsd-current@freebsd.org Mon Mar 18 15:30:56 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A72E01543EF0 for ; Mon, 18 Mar 2019 15:30:56 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D12848DC24; Mon, 18 Mar 2019 15:30:54 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id 5uDshtNauo7SQ5uDth9gy3; Mon, 18 Mar 2019 09:30:46 -0600 X-Authority-Analysis: v=2.3 cv=Go88BX9C c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=NTGMnVQrEZIA:10 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=vMSPLhnO7srFB-6dBi0A:9 a=QEXdDO2ut3YA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from android-68f84e02b5988183.esitwifi.local (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id 7F6D6340; Mon, 18 Mar 2019 08:30:43 -0700 (PDT) Date: Mon, 18 Mar 2019 08:30:42 -0700 User-Agent: K-9 Mail for Android In-Reply-To: <9c5eaa94-f55b-464a-ab0f-267e7fce4bd0@FreeBSD.org> References: <9c5eaa94-f55b-464a-ab0f-267e7fce4bd0@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: leaked swap? To: freebsd-current@freebsd.org, Andriy Gapon , FreeBSD Current From: Cy Schubert Message-ID: X-CMAE-Envelope: MS4wfObloWg/CXkfwHZhZJUiYjlVT1KAg5poqKTIodQ5kxI5VTU5iuCUOMb9ir64rmh/se87PTdS722kLu+eJg6WM0Y96GPXPhbXxHPloFQX+hIoo3QUm0e+ 5fYbOcHOryfZSJAzd2KWASOIdAN/6UUzosR35pSH+hHoAYSDXe44apAQndtXXip2iZrYHxDq3MkWooBNZI9MpOQ5YI9OjipSN80= X-Rspamd-Queue-Id: D12848DC24 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-4.37 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; MX_GOOD(-0.01)[cached: spqr.komquats.com]; NEURAL_HAM_SHORT(-0.94)[-0.943,0]; IP_SCORE(-2.21)[ip: (-5.84), ipnet: 64.59.128.0/20(-2.90), asn: 6327(-2.24), country: CA(-0.09)]; R_SPF_NA(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11,233.154.66.70.zen.spamhaus.org : 127.0.0.11]; RCVD_IN_DNSWL_LOW(-0.10)[137.136.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 18 Mar 2019 15:30:56 -0000 On March 18, 2019 8:20:35 AM PDT, Andriy Gapon wrote: > >First, a note that this was observed on a system that runs a fairly old >current >(~ 1 year old) with a fairly long uptime (> 6 months)=2E >I noticed that the system was nearly out of memory, 98% of swap was in >use, >there was less than 1 GB of free memory, several GBs of each of active, >inactive >and laundry memory, and many GBs of wired (mostly ZFS)=2E >I decided to pro-actively reboot the system, but to speed that up I put >the >system to the single-user mode (via shutdown) and then back to >multi-user=2E So, >there was no real hardware reboot and the kernel kept running=2E=20 >However, all >userland processes were terminated=2E > >To my surprise, even while in the single-user mode the swap utilization >didn't >go below 70%=2E Also, laundry memory remained in multi-GB area, but >let's ignore >this for now=2E > >I think that the swap could be used only for anonymous memory, so I >expected it >go to zero after the shutdown to the single user mode=2E >Does anyone have any ideas? >Maybe that's something that has already been fixed? >If not, any ideas on what to look for? >Thanks! I've had a hunch of this but haven't gone down this rabbit hole to investi= gate=2E Related, yesterday I performed a git gc --aggressive=2E Top did not= report any swap used by git and GB of swap were used=2E I think to help ad= dress this we need a reliable reporting tool=2E Obviously two separate symp= toms, not sure if the same cause=2E --=20 Pardon the typos and autocorrect, small keyboard in use=2E Cheers, Cy Schubert FreeBSD UNIX: Web: http://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E