From nobody Mon Jul 29 11:45:22 2024
X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WXc4B30Jfz5RqpW
	for <freebsd-stable@mlmmj.nyi.freebsd.org>; Mon, 29 Jul 2024 11:45:30 +0000 (UTC)
	(envelope-from SRS0=wAXB=O5=klop.ws=ronald-lists@realworks.nl)
Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24])
	(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 did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4WXc4B0cNpz4RR3
	for <freebsd-stable@freebsd.org>; Mon, 29 Jul 2024 11:45:30 +0000 (UTC)
	(envelope-from SRS0=wAXB=O5=klop.ws=ronald-lists@realworks.nl)
Authentication-Results: mx1.freebsd.org;
	none
Date: Mon, 29 Jul 2024 13:45:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2;
	t=1722253522;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=uQQ0w5GWypQu6hc8lOaXXGKJnrkkE17pPF4uRgt0Z/Q=;
	b=rwIZRvCtrFbttO2zCZN0tb3gUZygGLwJ21B4n/aoFGG5zN0Gubhm1Oxa7gZIafaJTfU13r
	avQveteWMZ4lGn7cJO1FH6FrR34MC7kecMyShqjaII8wvXIwpMjEYCyL5pOUefsD13/N6H
	DCO1USkGrXAcLkr/0Fe+GEvN5zSqfLdgVO2y4bHYLmR8FmNTFBqjgP561iAQHSJ0/Wn0mp
	j9iZtxkomtFQE8Mmr9YHAd4qMamlww1gpkdgeJ9XA0DP1yJNshZcoTvfaHHBp6OuUs4Xa/
	8UpqwX4fZDsj+QK1OvCVKofk8vVgKhpzL86wyP04vmwI5hADraazxcfdrB001Q==
From: Ronald Klop <ronald-lists@klop.ws>
To: Gareth de Vaux <stable@lordcow.org>
Cc: freebsd-stable@freebsd.org
Message-ID: <1660574701.5287.1722253522002@localhost>
In-Reply-To: <ZqdftQRp8uNlh1Vw@lordcow.org>
References: <ZqdftQRp8uNlh1Vw@lordcow.org>
Subject: Re: 12.4-STABLE to 13.3-STABLE upgrade
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-stable
List-Help: <mailto:stable+help@freebsd.org>
List-Post: <mailto:stable@freebsd.org>
List-Subscribe: <mailto:stable+subscribe@freebsd.org>
List-Unsubscribe: <mailto:stable+unsubscribe@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_5286_2000741326.1722253521998"
X-Mailer: Realworks (713.22)
Importance: Normal
X-Priority: 3 (Normal)
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]
X-Rspamd-Queue-Id: 4WXc4B0cNpz4RR3

------=_Part_5286_2000741326.1722253521998
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Van: Gareth de Vaux <stable@lordcow.org>
Datum: maandag, 29 juli 2024 11:24
Aan: freebsd-stable@freebsd.org
Onderwerp: 12.4-STABLE to 13.3-STABLE upgrade
> 
> Hi guys, I need to upgrade from 12.4-STABLE r373297 (27 Dec 2023) to 13.3-STABLE
> 
> Do I need to upgrade first to 13.0-RELEASE to bridge some compatibilities?
> 
> I'm worried for example about updating ZFS bootcode but actually downgrading
> to 13.0-RELEASE and bricking the system.
> 
> I assume I can then source upgrade from -RELEASE to -STABLE without issue.
>  
> 
> 
> 


Hi,

The bootcode is not touched by upgrading FreeBSD. Upgrading the bootcode is a separate manual step.
And as long as you do not run "zpool upgrade" the ZFS bootcode and pools will stay compatible.


If you want the pools to not be upgraded "accidentally" you can do something like "zpool set compatibility=freebsd-12.4 <pool-name>".
Different compatibility versions can be found here:
# ls -l /usr/share/zfs/compatibility.d/

You do not provide much information on your system or upgrade method so I can't predict other issues you might run into, but as far as ZFS is concerned I think your upgrade should be fine.

Regards,
Ronald.
 
------=_Part_5286_2000741326.1722253521998
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html><head></head><body><br>
<p><strong>Van:</strong> Gareth de Vaux &lt;stable@lordcow.org&gt;<br>
<strong>Datum:</strong> maandag, 29 juli 2024 11:24<br>
<strong>Aan:</strong> freebsd-stable@freebsd.org<br>
<strong>Onderwerp:</strong> 12.4-STABLE to 13.3-STABLE upgrade</p>

<blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px">
<div class="MessageRFC822Viewer" id="P">
<div class="TextPlainViewer" id="P.P">Hi guys, I need to upgrade from 12.4-STABLE r373297 (27 Dec 2023) to 13.3-STABLE<br>
<br>
Do I need to upgrade first to 13.0-RELEASE to bridge some compatibilities?<br>
<br>
I'm worried for example about updating ZFS bootcode but actually downgrading<br>
to 13.0-RELEASE and bricking the system.<br>
<br>
I assume I can then source upgrade from -RELEASE to -STABLE without issue.<br>
&nbsp;</div>

<hr></div>
</blockquote>
<br>
<br>
Hi,<br>
<br>
The bootcode is not touched by upgrading FreeBSD. Upgrading the bootcode is a separate manual step.<br>
And as long as you do not run "zpool upgrade" the ZFS bootcode and pools will stay compatible.<br>
<br>
<br>
If you want the pools to not be upgraded "accidentally" you can do something like "zpool set compatibility=freebsd-12.4 &lt;pool-name&gt;".<br>
Different compatibility versions can be found here:<br>
# ls -l /usr/share/zfs/compatibility.d/<br>
<br>
You do not provide much information on your system or upgrade method so I can't predict other issues you might run into, but as far as ZFS is concerned I think your upgrade should be fine.<br>
<br>
Regards,<br>
Ronald.<br>
&nbsp;</body></html>
------=_Part_5286_2000741326.1722253521998--