From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied: [PATCH installer] install: zfs: fix setting compression to 'off'
Date: Tue, 27 Feb 2024 16:43:33 +0100 [thread overview]
Message-ID: <cf258e12-d385-4c21-acb4-497231026826@proxmox.com> (raw)
In-Reply-To: <20240227091817.184817-1-c.heiss@proxmox.com>
Am 27/02/2024 um 10:17 schrieb Christoph Heiss:
> The default for the `compression` property in ZFS got changed ~2 years
> ago by
>
> 56fa4aa96 ("Default to ON for compression") [0]
>
> Support for setting this option originally got introduced into the
> installer in 2016 by
>
> c7779156 ("refactor disk setup, add advanced ZFS options") [1]
>
> where the default of 'off' was still correct.
>
> As the installer only set the property if it was *not* explicitly set
> to 'on', this actually regressed in the meantime.
>
> Thus just remove the conditional all together, as the definedness-check
> did not have any impact anyway (since $value gets set to 'on'
> regardless) and the latter just causes regressions like this one.
>
> Tested by installing once w/o the patch to confirm the report and once
> with the patch applied, checking `zfs get compression` on the freshly
> installed system.
>
> [0] https://github.com/openzfs/zfs/commit/56fa4aa96eb3875f254e93eaef646ea20ba187f9
> [1] https://git.proxmox.com/?p=pve-installer.git;a=commit;h=c7779156db5c38cf184e143de0cab534bd0a9cb1
>
> Reported-by: Friedrich Weber <f.weber@proxmox.com>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> Proxmox/Install.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
prev parent reply other threads:[~2024-02-27 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 9:17 [pve-devel] " Christoph Heiss
2024-02-27 15:43 ` Thomas Lamprecht [this message]
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=cf258e12-d385-4c21-acb4-497231026826@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.