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 <behlendorf1@llnl.gov>
Reviewed-by: Alek Pinchuk <apinchuk@axcient.com>
Signed-off-by: George Amanakis <gamanakis@gmail.com>
Closes #13675
Closes #13717
This commit is contained in:
George Amanakis
2022-08-23 02:42:01 +02:00
committed by GitHub
parent 17e212652d
commit 0c4064d9a0
9 changed files with 190 additions and 34 deletions
+3
View File
@@ -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 .