Date: Wed, 21 Oct 2020 08:53:07 +0200 From: Polytropon <freebsd@edvax.de> To: David Christensen <dpchrist@holgerdanske.com> 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> <alpine.BSF.2.21.9999.2010161722590.72530@fledge.watson.org> <b221d5c4-e247-6fea-e613-b03e94cda280@jschneider.net> <5f885b772d622_95aa2adab2b9c5b41576495c3@sirportly-app-02.mail> <5f8dad6c5225e_11f782aaeb993e5bc705b@sirportly-app-01.mail> <31b3314a-b035-305d-4136-18bc690fa6ae@holgerdanske.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201021085307.5a5ec9cb.freebsd>