From owner-freebsd-questions@freebsd.org Tue Oct 20 03:36:24 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D980744428E for ; Tue, 20 Oct 2020 03:36:24 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [IPv6:2001:470:0:19b::b869:801b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.holgerdanske.com", Issuer "www.holgerdanske.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CFfRq4Cg1z3S6j for ; Tue, 20 Oct 2020 03:36:23 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from 99.100.19.101 (99-100-19-101.lightspeed.frokca.sbcglobal.net [99.100.19.101]) by holgerdanske.com with ESMTPSA (TLS_AES_128_GCM_SHA256:TLSv1.3:Kx=any:Au=any:Enc=AESGCM(128):Mac=AEAD) (SMTP-AUTH username dpchrist@holgerdanske.com, mechanism PLAIN) for ; Mon, 19 Oct 2020 20:36:14 -0700 Subject: Re: FreeBSD using swap even though there's a lot of free memory To: freebsd-questions@freebsd.org References: <5f8d9d5e14b4c_dad82b12ba6585a44346f@sirportly-app-01.mail> <20201016195748.ffc15759b311a5feefc91ef5@sohara.org> <5f885b772d622_95aa2adab2b9c5b41576495c3@sirportly-app-02.mail> <5f8dad6c5225e_11f782aaeb993e5bc705b@sirportly-app-01.mail> From: David Christensen Message-ID: <31b3314a-b035-305d-4136-18bc690fa6ae@holgerdanske.com> Date: Mon, 19 Oct 2020 20:36:10 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <5f8dad6c5225e_11f782aaeb993e5bc705b@sirportly-app-01.mail> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4CFfRq4Cg1z3S6j X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of dpchrist@holgerdanske.com has no SPF policy when checking 2001:470:0:19b::b869:801b) smtp.mailfrom=dpchrist@holgerdanske.com X-Spamd-Result: default: False [1.86 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.32)[0.317]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.46)[0.461]; ARC_NA(0.00)[]; NEURAL_SPAM_LONG(0.18)[0.180]; DMARC_NA(0.00)[holgerdanske.com]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2020 03:36:24 -0000 On 2020-10-19 08:14, Twingly Customer Support wrote: > The following are the updates that was installed last Friday, which seems to have solved the problem: > > New packages to be INSTALLED: > bash-completion: 2.11,2 > glib: 2.66.0_1,1 > postgresql12-client: 12.4 > > Installed packages to be UPGRADED: > bash: 5.0.17 -> 5.0.18_3 > ca_root_nss: 3.56 -> 3.57 > fio: 3.20 -> 3.23 I'm glad the problem went away. :-) Updates and upgrades have broken my systems more times than I care to remember. Now, I take an image of the system drive before upgrading a machine. If an upgrade misbehaves, hopefully I will catch it quickly and can simply go back to the previous image. Otherwise, I need to include backup/ restore of system configuration files and/or data when re-imaging. Perhaps you should consider setting up a staging/ testing environment, update/ upgrade that, and run tests. If everything looks good, then upgrade the production environment. The length of your 'pkg upgrade' output suggests that you might want to upgrade more frequently. This should give you a smaller haystack to search if and when an upgrade causes problems. All of the above might be facilitated with virtualization and/or automation. David