From owner-freebsd-questions@freebsd.org Thu Oct 22 13:34:53 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 56BD6448F52 for ; Thu, 22 Oct 2020 13:34:53 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from smarthost01b.mail.zen.net.uk (smarthost01b.mail.zen.net.uk [212.23.1.3]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CH7dS251Tz3dMj for ; Thu, 22 Oct 2020 13:34:52 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from [82.71.56.121] (helo=curlew.localnet) by smarthost01b.mail.zen.net.uk with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1kVajy-0006zW-Af for freebsd-questions@freebsd.org; Thu, 22 Oct 2020 13:34:50 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Subject: Re: FreeBSD using swap even though there's a lot of free memory Date: Thu, 22 Oct 2020 14:34:02 +0100 Message-ID: <41114958.RqoaopZvpL@curlew> In-Reply-To: <20201021085307.5a5ec9cb.freebsd@edvax.de> References: <5f8d9d5e14b4c_dad82b12ba6585a44346f@sirportly-app-01.mail> <31b3314a-b035-305d-4136-18bc690fa6ae@holgerdanske.com> <20201021085307.5a5ec9cb.freebsd@edvax.de> MIME-Version: 1.0 X-Originating-smarthost01b-IP: [82.71.56.121] Feedback-ID: 82.71.56.121 X-Rspamd-Queue-Id: 4CH7dS251Tz3dMj X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 212.23.1.3 is neither permitted nor denied by domain of jmc-freebsd2@milibyte.co.uk) smtp.mailfrom=jmc-freebsd2@milibyte.co.uk X-Spamd-Result: default: False [2.85 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[212.23.1.3:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.88)[0.885]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; ARC_NA(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.64)[0.635]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_SPAM_LONG(0.53)[0.530]; DMARC_NA(0.00)[milibyte.co.uk]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; CTE_CASE(0.50)[]; ASN(0.00)[asn:13037, ipnet:212.23.0.0/19, country:GB]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MAILMAN_DEST(0.00)[freebsd-questions]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7Bit X-Content-Filtered-By: Mailman/MimeDel 2.1.33 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: Thu, 22 Oct 2020 13:34:53 -0000 On Wednesday, 21 October 2020 07:53:07 BST Polytropon wrote: > This is a great opportunity to integrate ZFS-based BEs (boot > environments) into the workflow. They allow you to easily > revert back changes caused by updates if required. Well worth doing. That approach has saved my neck a few times when things have gone pear shaped with dependency issues after pkg upgrade has reinstalled a few hundred packages. I normally create a new BE and chroot into it to do the upgrade. That way the running system isn't interrupted even if the upgrade goes disastrously wrong. If the upgrade looks OK it's then just a case of rebooting with the new BE at a convenient time. -- Mike Clarke