See also the thread at [0] for the initial discussion/idea.
Disabling checksums is considered an "extraordinarily bad idea" [1] (for
pretty obvious reason) and nobody should really ever use it.
Thus remove the option completely; just so that users cannot simply
disable checksum "for performance reasons" without knowing about the
implications of this.
As pointed out by Thomas, it can still be set to "off" after the
installation using the `zfs` tool, if really wanted.
[0] https://lists.proxmox.com/pipermail/pve-devel/2023-December/061188.html
[1] https://openzfs.github.io/openzfs-docs/Basic%20Concepts/Checksums.html#disabling-checksums
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
my $combo_checksum = Gtk3::ComboBoxText->new();
$combo_checksum->set_tooltip_text("zfs checksum algorithm for rpool dataset");
- my $csum_opts = ["on", "off", "fletcher4", "sha256"];
+ my $csum_opts = ["on", "fletcher4", "sha256"];
foreach my $opt (@$csum_opts) {
$combo_checksum->append($opt, $opt);
}
pub enum ZfsChecksumOption {
#[default]
On,
- Off,
Fletcher4,
Sha256,
}
pub const ZFS_CHECKSUM_OPTIONS: &[ZfsChecksumOption] = {
use ZfsChecksumOption::*;
- &[On, Off, Fletcher4, Sha256]
+ &[On, Fletcher4, Sha256]
};
#[derive(Clone, Debug)]