From owner-freebsd-stable@freebsd.org Wed Mar 17 15:24:19 2021 Return-Path: Delivered-To: freebsd-stable@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 3E12E56C63D for ; Wed, 17 Mar 2021 15:24:19 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.net (024-240-198-186.biz.spectrum.com [24.240.198.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "dweimer.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0v8L0R1Zz4X5J for ; Wed, 17 Mar 2021 15:24:17 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received-SPF: pass (webmail.dweimer.net: authenticated connection) receiver=webmail.dweimer.net; client-ip=10.9.5.1; helo=www.dweimer.net; envelope-from=dweimer@dweimer.net; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; Received: from www.dweimer.net (pfsense.dweimer.me [10.9.5.1]) (authenticated bits=0) by webmail.dweimer.net (8.16.1/8.16.1) with ESMTPSA id 12HFOBjO006599 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Wed, 17 Mar 2021 10:24:11 -0500 (CDT) (envelope-from dweimer@dweimer.net) MIME-Version: 1.0 Date: Wed, 17 Mar 2021 10:24:06 -0500 From: "Dean E. Weimer" To: freebsd-stable@freebsd.org Subject: Re: Updating to 13-stable and existing ZFS pools: any gotchas? Reply-To: dweimer@dweimer.net In-Reply-To: References: <9A253CE5-8144-427C-9192-AF3E9ADBA3B4@lassitu.de> User-Agent: Roundcube Webmail/1.4.11 Message-ID: <6e022fe28d6717caeed28dd142018385@dweimer.net> X-Sender: dweimer@dweimer.net Organization: dweimer.net Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4F0v8L0R1Zz4X5J X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.00 / 15.00]; HAS_REPLYTO(0.00)[dweimer@dweimer.net]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:24.240.198.184/29]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; DKIM_TRACE(0.00)[dweimer.net:+]; DMARC_POLICY_ALLOW(-0.50)[dweimer.net,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[24.240.198.186:from]; ASN(0.00)[asn:20115, ipnet:24.240.196.0/22, country:US]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[dweimer.net:s=2017.01.31]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[24.240.198.186:from:127.0.2.255]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2021 15:24:19 -0000 On 2021-03-17 9:59 am, tech-lists wrote: > On Sun, Mar 14, 2021 at 09:59:21AM +0100, Stefan Bethke wrote: >> I'm planning to upgrade three production machines with existing ZFS >> pools to 13-stable. Is there anything I need to pay attention to wrt >> OpenZFS? Or should it be fully transparent, apart from updating >> loader? >> >> My (limited) testing with VMs went without a hitch, but I want to make >> sure I don't paint myself into a corner. > > Hi, I'm interested in this as well. > > I'm not using root-on-zfs. The zpool is 5* spinning rust, the booting > media is ssd/ufs2. Is updating the bootcode only relevant for > root-on-zfs? I've not done that for a similarly configured desktop > system, and it seems to be running stable/13 fine. (the desktop was a > stable/12 to stable/13 upgrade). > > thanks, If you are not booting from zfs its seemless. Just remembe once you issue zpool upgrade you wont be able to go back to older version. If booting from ZFS, just update your boot loader. I have updated a couple of systems from 12.2-RELEASE-p3 to 13.0-RC2. One using UEFI and the other using legacy bios with no problems. for UEFI I mounted EFI Boot partition EFI update, New ZFS data set was mounted at ROOT, zpool is mirror. Updated both EFI partitions in case primary goes offline. zpool set bootfs=ssd/ROOT/13.0-RC2 ssd mount -t msdosfs /dev/ada0p1 /mnt cp ROOT/boot/loader.efi /mnt/EFI/BOOT/BOOTX64.efi umount /mnt mount -t msdosfs /dev/ada1p1 /mnt cp ROOT/boot/loader.efi /mnt/EFI/BOOT/BOOTX64.efi umount /mnt Legacy Bios, again new ZFS data set was mounted at ROOT, and zpool is mirror, updated both boot partitions zpool set bootfs=zroot/ROOT/13.0-RC2 zroot gpart bootcode -b ROOT/boot/pmbr -p ROOT/boot/gptzfsboot -i 1 ada0 gpart bootcode -b ROOT/boot/pmbr -p ROOT/boot/gptzfsboot -i 1 ada1 Everything worked as expected. -- Thanks, Dean E. Weimer http://www.dweimer.net/