From owner-freebsd-questions@freebsd.org Wed Oct 21 06:53:18 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 E14DD444920 for ; Wed, 21 Oct 2020 06:53:18 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (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 "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CGLmY5Gybz3gXt for ; Wed, 21 Oct 2020 06:53:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([94.222.202.172]) by mrelayeu.kundenserver.de (mreue107 [212.227.15.183]) with ESMTPA (Nemesis) id 1Mjjvp-1k1akJ1Gxf-00lEfO; Wed, 21 Oct 2020 08:53:08 +0200 Date: Wed, 21 Oct 2020 08:53:07 +0200 From: Polytropon To: David Christensen Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD using swap even though there's a lot of free memory Message-Id: <20201021085307.5a5ec9cb.freebsd@edvax.de> In-Reply-To: <31b3314a-b035-305d-4136-18bc690fa6ae@holgerdanske.com> References: <5f8d9d5e14b4c_dad82b12ba6585a44346f@sirportly-app-01.mail> <20201016195748.ffc15759b311a5feefc91ef5@sohara.org> <5f885b772d622_95aa2adab2b9c5b41576495c3@sirportly-app-02.mail> <5f8dad6c5225e_11f782aaeb993e5bc705b@sirportly-app-01.mail> <31b3314a-b035-305d-4136-18bc690fa6ae@holgerdanske.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:TubRACOdHY8NQyUsFA3Y1HIEueJwh38kGue/YarPVRaoGQinMbP lnXRKLkyZs/40ftwjJWzQ6qaCiaWFA2x2C8yN//n5EDNOa++jDFuIk92zR71J6A8PBqT+g0 wUtK5wc86w3LSVAqgN1tt8xYvU63YGnx6RLGMNL5qSi6JIUPG9Ug2+l3ILsoQOEsMwmrhaG qUAQYEFSMXqnBUHawjDTg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:y1QYTXtml+g=:ms4jLGekpYiyrfbAxaq9sX bx9k2GnXpNZJ3DwFKG1nKyVG+Uph9mgZkg76PZpLh67HETGoUuVQ2ROznfoz7FMvixwYI0Los Wo4LPeB1rf0cqqu0Bbg1MW2yVIE5OyuYxRk7JYo35cOyCHgAWeRtz5yULsJDdofhQVUCe/zny WpbBPTQ+KagqC+LU89k64o+UqoKFb5k90GrCZwddW8Kyfk3v2i9VjDCBXiuSjts8yGKJRNC72 cfjcSq9jbTJwVra5bBJjNEjM9/CcRIEdZstLWaFZKSwtpAhwuoQIGlArz6I2qe0onAyFLpHHQ kflhVapDU+lXRRklZdxt+/ZqOPRk9VHnMXYC96XQwVdP4ot9g+O8YVKypVd8SB0+9bhrkQanf viaHXr31YTNRujUMF7vMHxeuLGI0cGLete8h66nloDhBmIPaBrGlxRoon24f+ X-Rspamd-Queue-Id: 4CGLmY5Gybz3gXt X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.17.10) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [2.65 / 15.00]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RECEIVED_SPAMHAUS_PBL(0.00)[94.222.202.172:received]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.21)[0.208]; NEURAL_HAM_LONG(-0.00)[-0.002]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.04)[0.041]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[212.227.17.10:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.17.10:from]; 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: Wed, 21 Oct 2020 06:53:18 -0000 On Mon, 19 Oct 2020 20:36:10 -0700, David Christensen wrote: > 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. 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. > 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. This is also possible, and often a good suggestion, if you can actually create such a "secondary environment"; if you have to do everything in "live mode", BEs are probably the best solution. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...