From 0c4064d9a08ca2cf601ad1010e7cfd3f917cb991 Mon Sep 17 00:00:00 2001 From: George Amanakis Date: Tue, 23 Aug 2022 02:42:01 +0200 Subject: Fix zpool status in case of unloaded keys When scrubbing an encrypted filesystem with unloaded key still report an error in zpool status. Reviewed-by: Brian Behlendorf Reviewed-by: Alek Pinchuk Signed-off-by: George Amanakis Closes #13675 Closes #13717 --- man/man7/zpool-features.7 | 3 +++ 1 file changed, 3 insertions(+) (limited to 'man/man7/zpool-features.7') diff --git a/man/man7/zpool-features.7 b/man/man7/zpool-features.7 index 09f1e50de..0ff1a9a52 100644 --- a/man/man7/zpool-features.7 +++ b/man/man7/zpool-features.7 @@ -545,6 +545,9 @@ This feature enables the upgraded version of errlog, which required an on-disk error log format change. Now the error log of each head dataset is stored separately in the zap object and keyed by the head id. +In case of encrypted filesystems with unloaded keys or unmounted encrypted +filesystems we are unable to check their snapshots or clones for errors and +these will not be reported. With this feature enabled, every dataset affected by an error block is listed in the output of .Nm zpool Cm status . -- cgit v1.2.3