From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC PATCH installer] proxinstall, common: remove deprecated fletcher2 as zfs checksum algorithm
Date: Fri, 22 Dec 2023 11:52:24 +0100 [thread overview]
Message-ID: <20231222105244.715015-1-c.heiss@proxmox.com> (raw)
Fletcher-2 has long been deprecated and should not be used anymore
[0][1], so we probably should not offer it anymore too. It's been
deprecated since at least over 3 years, beyond that it's hard to find an
exact date.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
[0] https://openzfs.github.io/openzfs-docs/Basic%20Concepts/Checksums.html#checksum-algorithms
[1] https://people.freebsd.org/~asomers/fletcher.pdf
---
Sending this as RFC since it might warrant some discussions.
While digging into this a bit more, I reckon we should remove 'off' as
an option too. It's considered an "extraordinarily bad idea" [2] (for to
pretty obvious reason) and nobody should ever use it.
Might be a good idea, just so that users simply disable checksum "for
performance reasons" without knowing about the implications of this.
[2] https://openzfs.github.io/openzfs-docs/Basic%20Concepts/Checksums.html#disabling-checksums
proxinstall | 2 +-
proxmox-installer-common/src/options.rs | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/proxinstall b/proxinstall
index 01d4cfe..d6d5acb 100755
--- a/proxinstall
+++ b/proxinstall
@@ -1145,7 +1145,7 @@ my $create_raid_advanced_grid = sub {
my $combo_checksum = Gtk3::ComboBoxText->new();
$combo_checksum->set_tooltip_text("zfs checksum algorithm for rpool dataset");
- my $csum_opts = ["on", "off","fletcher2", "fletcher4", "sha256"];
+ my $csum_opts = ["on", "off", "fletcher4", "sha256"];
foreach my $opt (@$csum_opts) {
$combo_checksum->append($opt, $opt);
}
diff --git a/proxmox-installer-common/src/options.rs b/proxmox-installer-common/src/options.rs
index afd12cd..98cd907 100644
--- a/proxmox-installer-common/src/options.rs
+++ b/proxmox-installer-common/src/options.rs
@@ -146,7 +146,6 @@ pub enum ZfsChecksumOption {
#[default]
On,
Off,
- Fletcher2,
Fletcher4,
Sha256,
}
@@ -165,7 +164,7 @@ impl From<&ZfsChecksumOption> for String {
pub const ZFS_CHECKSUM_OPTIONS: &[ZfsChecksumOption] = {
use ZfsChecksumOption::*;
- &[On, Off, Fletcher2, Fletcher4, Sha256]
+ &[On, Off, Fletcher4, Sha256]
};
#[derive(Clone, Debug)]
--
2.42.0
next reply other threads:[~2023-12-22 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 10:52 Christoph Heiss [this message]
2024-02-06 12:17 ` [pve-devel] applied: " Thomas Lamprecht
2024-02-06 13:03 ` Christoph Heiss
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=20231222105244.715015-1-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pve-devel@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