all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 2/2] local-zfs: update the limitations of native encryption
Date: Wed, 18 Nov 2026 00:42:31 +0100	[thread overview]
Message-ID: <20261117234330.801935-9-t.lamprecht@proxmox.com> (raw)
In-Reply-To: <20261117234330.801935-1-t.lamprecht@proxmox.com>

Native ZFS encryption was marked experimental, citing two problems.
Replicating encrypted datasets was fixed with pve-storage 9.1.3, and
the OpenZFS issue about checksum errors with snapshots was closed in
May 2025 together with the send corruption it was traced to, fixed in
OpenZFS 2.2.8 and 2.3.3. The installer now offers native ZFS
encryption for the root pool.

So drop the experimental warning and note what stays readable instead.
Replace the statement that GRUB cannot boot from such pools with how
the installer sets that up, and mention zfs-mount-generator for
loading the keys of other encrypted datasets at boot.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
---
 local-zfs.adoc | 23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)

diff --git a/local-zfs.adoc b/local-zfs.adoc
index 029f628..0577440 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -702,11 +702,8 @@ improve performance when sufficient memory exists in a system.
 Encrypted ZFS Datasets
 ~~~~~~~~~~~~~~~~~~~~~~
 
-WARNING: Native ZFS encryption in {pve} is experimental. Known limitations and
-issues include Replication with encrypted datasets
-footnote:[https://bugzilla.proxmox.com/show_bug.cgi?id=2350],
-as well as checksum errors when using Snapshots or ZVOLs.
-footnote:[https://github.com/openzfs/zfs/issues/11688]
+NOTE: Native ZFS encryption leaves the names, properties and space usage of
+datasets and snapshots readable.
 
 ZFS on Linux version 0.8.0 introduced support for native encryption of
 datasets. After an upgrade from previous ZFS on Linux versions, the encryption
@@ -724,14 +721,16 @@ NAME  PROPERTY            VALUE            SOURCE
 tank  feature@encryption  enabled         local
 ----
 
-WARNING: There is currently no support for booting from pools with encrypted
-datasets using GRUB, and only limited support for automatically unlocking
-encrypted datasets on boot. Older versions of ZFS without encryption support
-will not be able to decrypt stored data.
+WARNING: GRUB cannot read encrypted datasets. For
+xref:installation_disk_encryption[full-disk encryption], the installer puts the
+kernels and initial RAM disks on unencrypted EFI system partitions managed by
+xref:sysboot_proxmox_boot_tool[`proxmox-boot-tool`]. Older versions of ZFS
+without encryption support will not be able to decrypt stored data.
 
-NOTE: It is recommended to either unlock storage datasets manually after
-booting, or to write a custom unit to pass the key material needed for
-unlocking on boot to `zfs load-key`.
+NOTE: Encrypted storage datasets with their own encryption root have to be
+unlocked manually after booting, or configured to load their key at boot, for
+example with the `zfs-load-key@` units of `zfs-mount-generator(8)` or a custom
+unit that passes the key material to `zfs load-key`.
 
 WARNING: Establish and test a backup procedure before enabling encryption of
 production data. If the associated key material/passphrase/keyfile has been
-- 
2.47.3





      parent reply	other threads:[~2026-11-17 23:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 23:42 [PATCH proxmox/installer/docs 0/8] installer: add full-disk encryption of the system disks Thomas Lamprecht
2026-11-17 23:42 ` [PATCH proxmox 1/1] installer-types: add full-disk encryption to the disk setup Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 1/5] install: encrypt the system disks with LUKS2 or native ZFS encryption Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 2/5] auto: support full-disk encryption in answer files Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 3/5] chroot enter: unlock the LUKS containers of an encrypted installation Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 4/5] ui: offer full-disk encryption in the graphical and terminal installer Thomas Lamprecht
2026-11-17 23:42 ` [PATCH installer 5/5] assistant: keep the disk passphrase out of prepared ISOs Thomas Lamprecht
2026-11-17 23:42 ` [PATCH docs 1/2] installation: describe full-disk encryption Thomas Lamprecht
2026-11-17 23:42 ` 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=20261117234330.801935-9-t.lamprecht@proxmox.com \
    --to=t.lamprecht@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal