From owner-freebsd-current@freebsd.org Mon Mar 22 02:20:11 2021 Return-Path: Delivered-To: freebsd-current@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 DFCC057635B; Mon, 22 Mar 2021 02:20:11 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F3dWG5pS2z4klZ; Mon, 22 Mar 2021 02:20:10 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-wm1-f41.google.com with SMTP id d8-20020a1c1d080000b029010f15546281so8165384wmd.4; Sun, 21 Mar 2021 19:20:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q2nnBIsqHqevMVmJAmaKJhI9lhwBNWSij3ekA3Q4KuA=; b=hCdG1LWdebr3R0VKLM0u7fON9rcHONJ13nD7RgBzR1ZBC/nc51yLOtoFntILhWytEF bqgVzNFNJxSvWHqeCUapWeOKbUZCeGgUQqQJhHW6JsopvLRNfYXeh4kim8DtJHgDsgLI AEjrDWpZl9bcyvk+6og0QPS40bqewPANENU85sIrrzvUQmS+9UsCjHBDYv3ryZuumfvo es9SlebyOQq/kvyolIzuFQ9RHucp0lC7xUtf0MDVaH0o0v4Otwk9QNefEDQLJMsEhtl/ y1aAbUH6w9GVeX1Ap1NOYXaZespWpUQZo2xa/M+EhuVBspdXtWfA1xovLy03v/6QxW3d f1AA== X-Gm-Message-State: AOAM5306htF0N1p77QCnU5Kl/UyvUgk6HSye+3Lyt0a1KW/7Woklpsje 1xZAhCzYlYoHzeoFloOa8oF3sA9F3eJAYH+kBJ/WwYv0D4I= X-Google-Smtp-Source: ABdhPJyakXESR3q+/1XZZONFnjQ9K+pQ6aNbdSzR/fXl4gmLfRra0udNwfBe2pKhexaZ0Y4Ls1LVr8W/UeneBZFgq0k= X-Received: by 2002:a1c:7fcd:: with SMTP id a196mr13947945wmd.180.1616379608905; Sun, 21 Mar 2021 19:20:08 -0700 (PDT) MIME-Version: 1.0 References: <20210320160853.GL92054@FreeBSD.org> In-Reply-To: <20210320160853.GL92054@FreeBSD.org> From: Jason Tubnor Date: Mon, 22 Mar 2021 13:19:57 +1100 Message-ID: Subject: Re: FreeBSD 13.0-RC3 Now Available To: Glen Barber Cc: FreeBSD CURRENT , freebsd-stable , freebsd-snapshots@freebsd.org, FreeBSD Release Engineering Team X-Rspamd-Queue-Id: 4F3dWG5pS2z4klZ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jtubnor@gmail.com designates 209.85.128.41 as permitted sender) smtp.mailfrom=jtubnor@gmail.com X-Spamd-Result: default: False [-2.45 / 15.00]; RCVD_TLS_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[tubnor.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.128.41:from]; RCPT_COUNT_FIVE(0.00)[5]; SPAMHAUS_ZRD(0.00)[209.85.128.41:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.45)[-0.454]; RCVD_IN_DNSWL_NONE(0.00)[209.85.128.41:from]; FORGED_SENDER(0.30)[jason@tubnor.net,jtubnor@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.128.41:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[jason@tubnor.net,jtubnor@gmail.com]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-stable,freebsd-snapshots]; RCVD_COUNT_TWO(0.00)[2] X-Mailman-Approved-At: Mon, 22 Mar 2021 06:31:21 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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, 22 Mar 2021 02:20:12 -0000 On Sun, 21 Mar 2021 at 03:08, Glen Barber wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > The third RC build of the 13.0-RELEASE release cycle is now available. > > === Upgrading === > > The freebsd-update(8) utility supports binary upgrades of amd64, i386, > and aarch64 systems running earlier FreeBSD releases. Systems running > earlier FreeBSD releases can upgrade as follows: > > # freebsd-update upgrade -r 13.0-RC3 > > During this process, freebsd-update(8) may ask the user to help by > merging some configuration files or by confirming that the automatically > performed merging was done correctly. > > # freebsd-update install > > The system must be rebooted with the newly installed kernel before > continuing. > > # shutdown -r now > > After rebooting, freebsd-update needs to be run again to install the new > userland components: > > # freebsd-update install > > It is recommended to rebuild and install all applications if possible, > especially if upgrading from an earlier FreeBSD release, for example, > FreeBSD 11.x. Alternatively, the user can install misc/compat11x and > other compatibility libraries, afterwards the system must be rebooted > into the new userland: > > # shutdown -r now > > Finally, after rebooting, freebsd-update needs to be run again to remove > stale files: > > # freebsd-update install Hi, There are two edge cases where the above update instructions will not work. 1) Due to the VLAN re-write in ifconfig(8), if a user is using a host that is fully utilising VLAN tagging, the machine will not be available on the network until the second reboot. The user will either need IPMI/LOM access to the console to execute the second 'freebsd-update install' command or have a way of it being executed and automatically rebooting prior to having access to the host on the network again. 2) If a user has a 12.2 zpool checkpoint in play and booting via BIOS legacy mode, the machine will hang at next reboot with 'zio_read error: 5' 'ZFS: i/o error - all block copies unavailable' 'ZFS: can not read checkpoint data.' The machine will have to be rebooted with a boot ISO and the checkpoint will need to be discarded and the system will boot correctly again (rewind has been unsuccessful). Please note: This does not appear to be an issue where hosts use UEFI for booting operating systems or if zpool checkpoints are destroyed prior to the update process. Cheers, Jason.