From: Mira Limbeck <m.limbeck@proxmox.com>
To: pve-devel@pve.proxmox.com
Subject: [pve-devel] [PATCH docs] add clarification of experimental zfs encryption status
Date: Wed, 6 Jul 2022 16:36:53 +0200 [thread overview]
Message-ID: <20220706143653.1712334-1-m.limbeck@proxmox.com> (raw)
Signed-off-by: Mira Limbeck <m.limbeck@proxmox.com>
---
local-zfs.adoc | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/local-zfs.adoc b/local-zfs.adoc
index 2dc25fd..1f4a4ed 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -547,6 +547,12 @@ 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]
+
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
feature can be enabled per pool:
--
2.30.2
next reply other threads:[~2022-07-06 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 14:36 Mira Limbeck [this message]
2022-07-12 7:09 ` [pve-devel] applied: " Thomas Lamprecht
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=20220706143653.1712334-1-m.limbeck@proxmox.com \
--to=m.limbeck@proxmox.com \
--cc=pve-devel@pve.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.