public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Jan Vlach <janus@volny.cz>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox VE 8.1 released!
Date: Thu, 23 Nov 2023 23:35:42 +0100	[thread overview]
Message-ID: <969ADBB0-ACE4-4136-AAB5-DC02802A4CA8@volny.cz> (raw)
In-Reply-To: <6b9a818d-1256-435e-bce3-c3a8dbcd6671@proxmox.com>

Hello Martin,

I'm sorry for stupid question, but I don't quite follow what the OpenZFS  2.2.0 with "the most important bugfixes from 2.2.1" means.

there is issue 15526 (https://github.com/openzfs/zfs/issues/15526 <https://github.com/openzfs/zfs/issues/15526>) in openzfs that enables block cloning feature by default and that on linux "eats" data.

OpenZFS 2.2.1 specifically switches the block cloning on by default to off by default and nothing else. ( https://github.com/openzfs/zfs/commit/479dca51c66a731e637bd2d4f9bba01a05f9ac9f <https://github.com/openzfs/zfs/commit/479dca51c66a731e637bd2d4f9bba01a05f9ac9f>  )

So is the code at 2.2.0 (toxic) eating data by default or at 2.2.1 where block cloning is disabled by default and therefore safe?

Thank you for clarification,
JV

> On 23. 11. 2023, at 15:27, Martin Maurer <martin@proxmox.com> wrote:
> 
> We're very excited to announce the release 8.1 of Proxmox Virtual Environment! It's based on Debian 12.2 "Bookworm" but uses a newer Linux kernel 6.5, QEMU 8.1.2, and OpenZFS 2.2.0 ((with stable fixes backported)
> 
> Here is a selection of the highlights of Proxmox VE 8.1
> 
> - Debian 12.2 (“Bookworm”), but uses a newer Linux kernel 6.5 as stable default
> - latest versions of QEMU 8.1.2 and ZFS 2.2.0 including the most important bugfixes from 2.2.1 already
> - Software-defined Networking (SDN)
> - Secure Boot
> - New flexible notification system with matcher-based approach
> - Ceph Server: Ceph Reef 18.2.0 is default, and Ceph Quincy 17.2.7 comes with continued support.
> -Countless GUI and API improvements.
> 
> As always, we have included countless bugfixes and improvements on many places; see the release notes for all details.
> 
> Release notes
> https://pve.proxmox.com/wiki/Roadmap
> 
> Press release
> https://www.proxmox.com/en/news/press-releases/
> 
> Video tutorial
> https://www.proxmox.com/en/training/video-tutorials/item/what-s-new-in-proxmox-ve-8-1
> 
> Download
> https://www.proxmox.com/en/downloads
> Alternate ISO download:
> https://enterprise.proxmox.com/iso
> 
> Documentation
> https://pve.proxmox.com/pve-docs
> 
> Community Forum
> https://forum.proxmox.com
> 
> Bugtracker
> https://bugzilla.proxmox.com
> 
> Source code
> https://git.proxmox.com
> 
> There has been a lot of feedback from our community members and customers, and many of you reported bugs, submitted patches and were involved in testing - THANK YOU for your support!
> 
> FAQ
> 
> Q: Can I upgrade latest Proxmox VE 7 to 8 with apt?
> A: Yes, please follow the upgrade instructions on https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
> 
> Q: Can I upgrade an 8.0 installation to the stable 8.1 via apt?
> A: Yes, upgrading from is possible via apt and GUI.
> 
> Q: Can I install Proxmox VE 8.1 on top of Debian 12 "Bookworm"?
> A: Yes, see https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm
> 
> Q: Can I upgrade my Proxmox VE 7.4 cluster with Ceph Pacific to Proxmox VE 8.1 and to Ceph Reef?
> A: This is a three-step process. First, you have to upgrade Ceph from Pacific to Quincy, and afterwards you can then upgrade Proxmox VE from 7.4 to 8.1. As soon as you run Proxmox VE 8.1, you can upgrade Ceph to Reef. There are a lot of improvements and changes, so please follow exactly the upgrade documentation:
> https://pve.proxmox.com/wiki/Ceph_Pacific_to_Quincy
> https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
> https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef
> 
> Q: Where can I get more information about feature updates?
> A: Check the roadmap, forum, the mailing list, and/or subscribe to our newsletter.
> 
> -- 
> Best Regards,
> 
> Martin Maurer
> Proxmox VE project leader
> 
> 
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user



  reply	other threads:[~2023-11-23 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 14:27 Martin Maurer
2023-11-23 22:35 ` Jan Vlach [this message]
2023-11-23 22:43   ` Jan Vlach
     [not found]     ` <mailman.293.1700812718.422.pve-user@lists.proxmox.com>
2023-11-24  8:12       ` Fabian Grünbichler
     [not found]         ` <mailman.296.1700814059.422.pve-user@lists.proxmox.com>
2023-11-24  8:32           ` Fabian Grünbichler
2023-11-24 14:24           ` Jan Vlach
2023-11-24  7:27   ` Fabian Grünbichler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=969ADBB0-ACE4-4136-AAB5-DC02802A4CA8@volny.cz \
    --to=janus@volny.cz \
    --cc=pve-devel@lists.proxmox.com \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal