Increase meta-dnode redundancy in "some" mode

Loss of one indirect block of the meta dnode likely means loss of
the whole dataset.  It is worse than one file that the man page
promises, and in my opinion is not much better than "none" mode.

This change restores redundancy of the meta-dnode indirect blocks,
while same time still corrects expectations in the man page.

Reviewed-by: Akash B <akash-b@hpe.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Rob Norris <robn@despairlabs.com>
Signed-off-by:	Alexander Motin <mav@FreeBSD.org>
Sponsored by:	iXsystems, Inc.
Closes #17339
This commit is contained in:
Alexander Motin
2025-05-16 13:23:32 -04:00
committed by Alexander Motin
parent fd5a27c9db
commit 30fa92bff3
3 changed files with 5 additions and 4 deletions
+1 -1
View File
@@ -2368,7 +2368,7 @@ dmu_write_policy(objset_t *os, dnode_t *dn, int level, int wp, zio_prop_t *zp)
gang_copies++;
break;
case ZFS_REDUNDANT_METADATA_SOME:
if (DMU_OT_IS_CRITICAL(type)) {
if (DMU_OT_IS_CRITICAL(type, level)) {
copies++;
gang_copies++;
} else if (DMU_OT_IS_METADATA(type)) {