feedback

Signed-off-by: Paul Dagnelie <[email protected]>

Author: Paul Dagnelie

man/man4/zfs.4

@@ -1778,7 +1778,7 @@ Normally disabled because these datasets may be missing key data.
 .It Sy zfs_min_metaslabs_to_flush Ns = Ns Sy 1 Pq u64
 Minimum number of metaslabs to flush per dirty TXG.
 .
-.It Sy zfs_metaslab_fragmentation_threshold Ns = Ns Sy 85 Ns % Pq uint
+.It Sy zfs_metaslab_fragmentation_threshold Ns = Ns Sy 77 Ns % Pq uint
 Allow metaslabs to keep their active state as long as their fragmentation
 percentage is no more than this value.
 An active metaslab that exceeds this threshold

module/zfs/metaslab.c

@@ -146,7 +146,7 @@ static uint_t zfs_mg_fragmentation_threshold = 95;
  * active metaslab that exceeds this threshold will no longer keep its active
  * status allowing better metaslabs to be selected.
  */
-static uint_t zfs_metaslab_fragmentation_threshold = 85;
+static uint_t zfs_metaslab_fragmentation_threshold = 77;
 
 /*
  * When set will load all metaslabs when pool is first opened.
@@ -2901,7 +2901,7 @@ metaslab_fini(metaslab_t *msp)
  * Conversely, if the metric is low, then most of the free space is in
  * large segments.
  *
- * This table defines 0% fragmented space using 1G segments. Using this value,
+ * This table defines 0% fragmented space using 512M segments. Using this value,
  * we derive the rest of the table. This table originally went up to 16MB, but
  * with larger recordsizes, larger ashifts, and use of raidz3, it is possible
  * to have significantly larger allocations than were previously possible.