From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <f.gruenbichler@proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 6C5C59D78C
 for <pve-user@lists.proxmox.com>; Fri, 24 Nov 2023 09:32:33 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 4EC4BA044
 for <pve-user@lists.proxmox.com>; Fri, 24 Nov 2023 09:32:03 +0100 (CET)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [94.136.29.106])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS
 for <pve-user@lists.proxmox.com>; Fri, 24 Nov 2023 09:32:02 +0100 (CET)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
 by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 8965D43A6C;
 Fri, 24 Nov 2023 09:32:02 +0100 (CET)
Date: Fri, 24 Nov 2023 09:32:01 +0100 (CET)
From: =?UTF-8?Q?Fabian_Gr=C3=BCnbichler?= <f.gruenbichler@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Message-ID: <2139359655.1481.1700814721888@webmail.proxmox.com>
In-Reply-To: <mailman.296.1700814059.422.pve-user@lists.proxmox.com>
References: <6b9a818d-1256-435e-bce3-c3a8dbcd6671@proxmox.com>
 <969ADBB0-ACE4-4136-AAB5-DC02802A4CA8@volny.cz>
 <18793296-4C84-4345-B1D5-35E472D9278F@volny.cz>
 <mailman.293.1700812718.422.pve-user@lists.proxmox.com>
 <1624311989.1471.1700813540249@webmail.proxmox.com>
 <mailman.296.1700814059.422.pve-user@lists.proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev54
X-Originating-Client: open-xchange-appsuite
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.065 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
 T_SCC_BODY_TEXT_LINE    -0.01 -
Subject: Re: [PVE-User] Proxmox VE 8.1 released!
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Fri, 24 Nov 2023 08:32:33 -0000

> So if we patch to Proxmox 8.1 (zfs 2.2.0-pve3) and disable "feature@block_cloning" or don't do a pool upgrade, would we have a current reliable state?

PVE 8.1 comes with ZFS with block cloning disabled by default (this was cherry-picked from ZFS 2.2.1, even though PVE comes with 2.2.0). There is no other issue that is known at the moment that would be worse with 2.2 compared to 2.1 or 2.0.