xref: /freebsd/sys/contrib/openzfs/man/man4/zfs.4 (revision 357378bbdedf24ce2b90e9bd831af4a9db3ec70a)
1.\"
2.\" Copyright (c) 2013 by Turbo Fredriksson <turbo@bayour.com>. All rights reserved.
3.\" Copyright (c) 2019, 2021 by Delphix. All rights reserved.
4.\" Copyright (c) 2019 Datto Inc.
5.\" Copyright (c) 2023, 2024 Klara, Inc.
6.\" The contents of this file are subject to the terms of the Common Development
7.\" and Distribution License (the "License").  You may not use this file except
8.\" in compliance with the License. You can obtain a copy of the license at
9.\" usr/src/OPENSOLARIS.LICENSE or https://opensource.org/licenses/CDDL-1.0.
10.\"
11.\" See the License for the specific language governing permissions and
12.\" limitations under the License. When distributing Covered Code, include this
13.\" CDDL HEADER in each file and include the License file at
14.\" usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this
15.\" CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your
16.\" own identifying information:
17.\" Portions Copyright [yyyy] [name of copyright owner]
18.\"
19.Dd June 27, 2024
20.Dt ZFS 4
21.Os
22.
23.Sh NAME
24.Nm zfs
25.Nd tuning of the ZFS kernel module
26.
27.Sh DESCRIPTION
28The ZFS module supports these parameters:
29.Bl -tag -width Ds
30.It Sy dbuf_cache_max_bytes Ns = Ns Sy UINT64_MAX Ns B Pq u64
31Maximum size in bytes of the dbuf cache.
32The target size is determined by the MIN versus
33.No 1/2^ Ns Sy dbuf_cache_shift Pq 1/32nd
34of the target ARC size.
35The behavior of the dbuf cache and its associated settings
36can be observed via the
37.Pa /proc/spl/kstat/zfs/dbufstats
38kstat.
39.
40.It Sy dbuf_metadata_cache_max_bytes Ns = Ns Sy UINT64_MAX Ns B Pq u64
41Maximum size in bytes of the metadata dbuf cache.
42The target size is determined by the MIN versus
43.No 1/2^ Ns Sy dbuf_metadata_cache_shift Pq 1/64th
44of the target ARC size.
45The behavior of the metadata dbuf cache and its associated settings
46can be observed via the
47.Pa /proc/spl/kstat/zfs/dbufstats
48kstat.
49.
50.It Sy dbuf_cache_hiwater_pct Ns = Ns Sy 10 Ns % Pq uint
51The percentage over
52.Sy dbuf_cache_max_bytes
53when dbufs must be evicted directly.
54.
55.It Sy dbuf_cache_lowater_pct Ns = Ns Sy 10 Ns % Pq uint
56The percentage below
57.Sy dbuf_cache_max_bytes
58when the evict thread stops evicting dbufs.
59.
60.It Sy dbuf_cache_shift Ns = Ns Sy 5 Pq uint
61Set the size of the dbuf cache
62.Pq Sy dbuf_cache_max_bytes
63to a log2 fraction of the target ARC size.
64.
65.It Sy dbuf_metadata_cache_shift Ns = Ns Sy 6 Pq uint
66Set the size of the dbuf metadata cache
67.Pq Sy dbuf_metadata_cache_max_bytes
68to a log2 fraction of the target ARC size.
69.
70.It Sy dbuf_mutex_cache_shift Ns = Ns Sy 0 Pq uint
71Set the size of the mutex array for the dbuf cache.
72When set to
73.Sy 0
74the array is dynamically sized based on total system memory.
75.
76.It Sy dmu_object_alloc_chunk_shift Ns = Ns Sy 7 Po 128 Pc Pq uint
77dnode slots allocated in a single operation as a power of 2.
78The default value minimizes lock contention for the bulk operation performed.
79.
80.It Sy dmu_prefetch_max Ns = Ns Sy 134217728 Ns B Po 128 MiB Pc Pq uint
81Limit the amount we can prefetch with one call to this amount in bytes.
82This helps to limit the amount of memory that can be used by prefetching.
83.
84.It Sy ignore_hole_birth Pq int
85Alias for
86.Sy send_holes_without_birth_time .
87.
88.It Sy l2arc_feed_again Ns = Ns Sy 1 Ns | Ns 0 Pq int
89Turbo L2ARC warm-up.
90When the L2ARC is cold the fill interval will be set as fast as possible.
91.
92.It Sy l2arc_feed_min_ms Ns = Ns Sy 200 Pq u64
93Min feed interval in milliseconds.
94Requires
95.Sy l2arc_feed_again Ns = Ns Ar 1
96and only applicable in related situations.
97.
98.It Sy l2arc_feed_secs Ns = Ns Sy 1 Pq u64
99Seconds between L2ARC writing.
100.
101.It Sy l2arc_headroom Ns = Ns Sy 8 Pq u64
102How far through the ARC lists to search for L2ARC cacheable content,
103expressed as a multiplier of
104.Sy l2arc_write_max .
105ARC persistence across reboots can be achieved with persistent L2ARC
106by setting this parameter to
107.Sy 0 ,
108allowing the full length of ARC lists to be searched for cacheable content.
109.
110.It Sy l2arc_headroom_boost Ns = Ns Sy 200 Ns % Pq u64
111Scales
112.Sy l2arc_headroom
113by this percentage when L2ARC contents are being successfully compressed
114before writing.
115A value of
116.Sy 100
117disables this feature.
118.
119.It Sy l2arc_exclude_special Ns = Ns Sy 0 Ns | Ns 1 Pq int
120Controls whether buffers present on special vdevs are eligible for caching
121into L2ARC.
122If set to 1, exclude dbufs on special vdevs from being cached to L2ARC.
123.
124.It Sy l2arc_mfuonly Ns = Ns Sy 0 Ns | Ns 1 Pq  int
125Controls whether only MFU metadata and data are cached from ARC into L2ARC.
126This may be desired to avoid wasting space on L2ARC when reading/writing large
127amounts of data that are not expected to be accessed more than once.
128.Pp
129The default is off,
130meaning both MRU and MFU data and metadata are cached.
131When turning off this feature, some MRU buffers will still be present
132in ARC and eventually cached on L2ARC.
133.No If Sy l2arc_noprefetch Ns = Ns Sy 0 ,
134some prefetched buffers will be cached to L2ARC, and those might later
135transition to MRU, in which case the
136.Sy l2arc_mru_asize No arcstat will not be Sy 0 .
137.Pp
138Regardless of
139.Sy l2arc_noprefetch ,
140some MFU buffers might be evicted from ARC,
141accessed later on as prefetches and transition to MRU as prefetches.
142If accessed again they are counted as MRU and the
143.Sy l2arc_mru_asize No arcstat will not be Sy 0 .
144.Pp
145The ARC status of L2ARC buffers when they were first cached in
146L2ARC can be seen in the
147.Sy l2arc_mru_asize , Sy l2arc_mfu_asize , No and Sy l2arc_prefetch_asize
148arcstats when importing the pool or onlining a cache
149device if persistent L2ARC is enabled.
150.Pp
151The
152.Sy evict_l2_eligible_mru
153arcstat does not take into account if this option is enabled as the information
154provided by the
155.Sy evict_l2_eligible_m[rf]u
156arcstats can be used to decide if toggling this option is appropriate
157for the current workload.
158.
159.It Sy l2arc_meta_percent Ns = Ns Sy 33 Ns % Pq uint
160Percent of ARC size allowed for L2ARC-only headers.
161Since L2ARC buffers are not evicted on memory pressure,
162too many headers on a system with an irrationally large L2ARC
163can render it slow or unusable.
164This parameter limits L2ARC writes and rebuilds to achieve the target.
165.
166.It Sy l2arc_trim_ahead Ns = Ns Sy 0 Ns % Pq u64
167Trims ahead of the current write size
168.Pq Sy l2arc_write_max
169on L2ARC devices by this percentage of write size if we have filled the device.
170If set to
171.Sy 100
172we TRIM twice the space required to accommodate upcoming writes.
173A minimum of
174.Sy 64 MiB
175will be trimmed.
176It also enables TRIM of the whole L2ARC device upon creation
177or addition to an existing pool or if the header of the device is
178invalid upon importing a pool or onlining a cache device.
179A value of
180.Sy 0
181disables TRIM on L2ARC altogether and is the default as it can put significant
182stress on the underlying storage devices.
183This will vary depending of how well the specific device handles these commands.
184.
185.It Sy l2arc_noprefetch Ns = Ns Sy 1 Ns | Ns 0 Pq int
186Do not write buffers to L2ARC if they were prefetched but not used by
187applications.
188In case there are prefetched buffers in L2ARC and this option
189is later set, we do not read the prefetched buffers from L2ARC.
190Unsetting this option is useful for caching sequential reads from the
191disks to L2ARC and serve those reads from L2ARC later on.
192This may be beneficial in case the L2ARC device is significantly faster
193in sequential reads than the disks of the pool.
194.Pp
195Use
196.Sy 1
197to disable and
198.Sy 0
199to enable caching/reading prefetches to/from L2ARC.
200.
201.It Sy l2arc_norw Ns = Ns Sy 0 Ns | Ns 1 Pq int
202No reads during writes.
203.
204.It Sy l2arc_write_boost Ns = Ns Sy 33554432 Ns B Po 32 MiB Pc Pq u64
205Cold L2ARC devices will have
206.Sy l2arc_write_max
207increased by this amount while they remain cold.
208.
209.It Sy l2arc_write_max Ns = Ns Sy 33554432 Ns B Po 32 MiB Pc Pq u64
210Max write bytes per interval.
211.
212.It Sy l2arc_rebuild_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
213Rebuild the L2ARC when importing a pool (persistent L2ARC).
214This can be disabled if there are problems importing a pool
215or attaching an L2ARC device (e.g. the L2ARC device is slow
216in reading stored log metadata, or the metadata
217has become somehow fragmented/unusable).
218.
219.It Sy l2arc_rebuild_blocks_min_l2size Ns = Ns Sy 1073741824 Ns B Po 1 GiB Pc Pq u64
220Mininum size of an L2ARC device required in order to write log blocks in it.
221The log blocks are used upon importing the pool to rebuild the persistent L2ARC.
222.Pp
223For L2ARC devices less than 1 GiB, the amount of data
224.Fn l2arc_evict
225evicts is significant compared to the amount of restored L2ARC data.
226In this case, do not write log blocks in L2ARC in order not to waste space.
227.
228.It Sy metaslab_aliquot Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq u64
229Metaslab granularity, in bytes.
230This is roughly similar to what would be referred to as the "stripe size"
231in traditional RAID arrays.
232In normal operation, ZFS will try to write this amount of data to each disk
233before moving on to the next top-level vdev.
234.
235.It Sy metaslab_bias_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
236Enable metaslab group biasing based on their vdevs' over- or under-utilization
237relative to the pool.
238.
239.It Sy metaslab_force_ganging Ns = Ns Sy 16777217 Ns B Po 16 MiB + 1 B Pc Pq u64
240Make some blocks above a certain size be gang blocks.
241This option is used by the test suite to facilitate testing.
242.
243.It Sy metaslab_force_ganging_pct Ns = Ns Sy 3 Ns % Pq uint
244For blocks that could be forced to be a gang block (due to
245.Sy metaslab_force_ganging ) ,
246force this many of them to be gang blocks.
247.
248.It Sy brt_zap_prefetch Ns = Ns Sy 1 Ns | Ns 0 Pq int
249Controls prefetching BRT records for blocks which are going to be cloned.
250.
251.It Sy brt_zap_default_bs Ns = Ns Sy 12 Po 4 KiB Pc Pq int
252Default BRT ZAP data block size as a power of 2. Note that changing this after
253creating a BRT on the pool will not affect existing BRTs, only newly created
254ones.
255.
256.It Sy brt_zap_default_ibs Ns = Ns Sy 12 Po 4 KiB Pc Pq int
257Default BRT ZAP indirect block size as a power of 2. Note that changing this
258after creating a BRT on the pool will not affect existing BRTs, only newly
259created ones.
260.
261.It Sy ddt_zap_default_bs Ns = Ns Sy 15 Po 32 KiB Pc Pq int
262Default DDT ZAP data block size as a power of 2. Note that changing this after
263creating a DDT on the pool will not affect existing DDTs, only newly created
264ones.
265.
266.It Sy ddt_zap_default_ibs Ns = Ns Sy 15 Po 32 KiB Pc Pq int
267Default DDT ZAP indirect block size as a power of 2. Note that changing this
268after creating a DDT on the pool will not affect existing DDTs, only newly
269created ones.
270.
271.It Sy zfs_default_bs Ns = Ns Sy 9 Po 512 B Pc Pq int
272Default dnode block size as a power of 2.
273.
274.It Sy zfs_default_ibs Ns = Ns Sy 17 Po 128 KiB Pc Pq int
275Default dnode indirect block size as a power of 2.
276.
277.It Sy zfs_history_output_max Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq u64
278When attempting to log an output nvlist of an ioctl in the on-disk history,
279the output will not be stored if it is larger than this size (in bytes).
280This must be less than
281.Sy DMU_MAX_ACCESS Pq 64 MiB .
282This applies primarily to
283.Fn zfs_ioc_channel_program Pq cf. Xr zfs-program 8 .
284.
285.It Sy zfs_keep_log_spacemaps_at_export Ns = Ns Sy 0 Ns | Ns 1 Pq int
286Prevent log spacemaps from being destroyed during pool exports and destroys.
287.
288.It Sy zfs_metaslab_segment_weight_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
289Enable/disable segment-based metaslab selection.
290.
291.It Sy zfs_metaslab_switch_threshold Ns = Ns Sy 2 Pq int
292When using segment-based metaslab selection, continue allocating
293from the active metaslab until this option's
294worth of buckets have been exhausted.
295.
296.It Sy metaslab_debug_load Ns = Ns Sy 0 Ns | Ns 1 Pq int
297Load all metaslabs during pool import.
298.
299.It Sy metaslab_debug_unload Ns = Ns Sy 0 Ns | Ns 1 Pq int
300Prevent metaslabs from being unloaded.
301.
302.It Sy metaslab_fragmentation_factor_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
303Enable use of the fragmentation metric in computing metaslab weights.
304.
305.It Sy metaslab_df_max_search Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq uint
306Maximum distance to search forward from the last offset.
307Without this limit, fragmented pools can see
308.Em >100`000
309iterations and
310.Fn metaslab_block_picker
311becomes the performance limiting factor on high-performance storage.
312.Pp
313With the default setting of
314.Sy 16 MiB ,
315we typically see less than
316.Em 500
317iterations, even with very fragmented
318.Sy ashift Ns = Ns Sy 9
319pools.
320The maximum number of iterations possible is
321.Sy metaslab_df_max_search / 2^(ashift+1) .
322With the default setting of
323.Sy 16 MiB
324this is
325.Em 16*1024 Pq with Sy ashift Ns = Ns Sy 9
326or
327.Em 2*1024 Pq with Sy ashift Ns = Ns Sy 12 .
328.
329.It Sy metaslab_df_use_largest_segment Ns = Ns Sy 0 Ns | Ns 1 Pq int
330If not searching forward (due to
331.Sy metaslab_df_max_search , metaslab_df_free_pct ,
332.No or Sy metaslab_df_alloc_threshold ) ,
333this tunable controls which segment is used.
334If set, we will use the largest free segment.
335If unset, we will use a segment of at least the requested size.
336.
337.It Sy zfs_metaslab_max_size_cache_sec Ns = Ns Sy 3600 Ns s Po 1 hour Pc Pq u64
338When we unload a metaslab, we cache the size of the largest free chunk.
339We use that cached size to determine whether or not to load a metaslab
340for a given allocation.
341As more frees accumulate in that metaslab while it's unloaded,
342the cached max size becomes less and less accurate.
343After a number of seconds controlled by this tunable,
344we stop considering the cached max size and start
345considering only the histogram instead.
346.
347.It Sy zfs_metaslab_mem_limit Ns = Ns Sy 25 Ns % Pq uint
348When we are loading a new metaslab, we check the amount of memory being used
349to store metaslab range trees.
350If it is over a threshold, we attempt to unload the least recently used metaslab
351to prevent the system from clogging all of its memory with range trees.
352This tunable sets the percentage of total system memory that is the threshold.
353.
354.It Sy zfs_metaslab_try_hard_before_gang Ns = Ns Sy 0 Ns | Ns 1 Pq int
355.Bl -item -compact
356.It
357If unset, we will first try normal allocation.
358.It
359If that fails then we will do a gang allocation.
360.It
361If that fails then we will do a "try hard" gang allocation.
362.It
363If that fails then we will have a multi-layer gang block.
364.El
365.Pp
366.Bl -item -compact
367.It
368If set, we will first try normal allocation.
369.It
370If that fails then we will do a "try hard" allocation.
371.It
372If that fails we will do a gang allocation.
373.It
374If that fails we will do a "try hard" gang allocation.
375.It
376If that fails then we will have a multi-layer gang block.
377.El
378.
379.It Sy zfs_metaslab_find_max_tries Ns = Ns Sy 100 Pq uint
380When not trying hard, we only consider this number of the best metaslabs.
381This improves performance, especially when there are many metaslabs per vdev
382and the allocation can't actually be satisfied
383(so we would otherwise iterate all metaslabs).
384.
385.It Sy zfs_vdev_default_ms_count Ns = Ns Sy 200 Pq uint
386When a vdev is added, target this number of metaslabs per top-level vdev.
387.
388.It Sy zfs_vdev_default_ms_shift Ns = Ns Sy 29 Po 512 MiB Pc Pq uint
389Default lower limit for metaslab size.
390.
391.It Sy zfs_vdev_max_ms_shift Ns = Ns Sy 34 Po 16 GiB Pc Pq uint
392Default upper limit for metaslab size.
393.
394.It Sy zfs_vdev_max_auto_ashift Ns = Ns Sy 14 Pq uint
395Maximum ashift used when optimizing for logical \[->] physical sector size on
396new
397top-level vdevs.
398May be increased up to
399.Sy ASHIFT_MAX Po 16 Pc ,
400but this may negatively impact pool space efficiency.
401.
402.It Sy zfs_vdev_min_auto_ashift Ns = Ns Sy ASHIFT_MIN Po 9 Pc Pq uint
403Minimum ashift used when creating new top-level vdevs.
404.
405.It Sy zfs_vdev_min_ms_count Ns = Ns Sy 16 Pq uint
406Minimum number of metaslabs to create in a top-level vdev.
407.
408.It Sy vdev_validate_skip Ns = Ns Sy 0 Ns | Ns 1 Pq int
409Skip label validation steps during pool import.
410Changing is not recommended unless you know what you're doing
411and are recovering a damaged label.
412.
413.It Sy zfs_vdev_ms_count_limit Ns = Ns Sy 131072 Po 128k Pc Pq uint
414Practical upper limit of total metaslabs per top-level vdev.
415.
416.It Sy metaslab_preload_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
417Enable metaslab group preloading.
418.
419.It Sy metaslab_preload_limit Ns = Ns Sy 10 Pq uint
420Maximum number of metaslabs per group to preload
421.
422.It Sy metaslab_preload_pct Ns = Ns Sy 50 Pq uint
423Percentage of CPUs to run a metaslab preload taskq
424.
425.It Sy metaslab_lba_weighting_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
426Give more weight to metaslabs with lower LBAs,
427assuming they have greater bandwidth,
428as is typically the case on a modern constant angular velocity disk drive.
429.
430.It Sy metaslab_unload_delay Ns = Ns Sy 32 Pq uint
431After a metaslab is used, we keep it loaded for this many TXGs, to attempt to
432reduce unnecessary reloading.
433Note that both this many TXGs and
434.Sy metaslab_unload_delay_ms
435milliseconds must pass before unloading will occur.
436.
437.It Sy metaslab_unload_delay_ms Ns = Ns Sy 600000 Ns ms Po 10 min Pc Pq uint
438After a metaslab is used, we keep it loaded for this many milliseconds,
439to attempt to reduce unnecessary reloading.
440Note, that both this many milliseconds and
441.Sy metaslab_unload_delay
442TXGs must pass before unloading will occur.
443.
444.It Sy reference_history Ns = Ns Sy 3 Pq uint
445Maximum reference holders being tracked when reference_tracking_enable is
446active.
447.It Sy raidz_expand_max_copy_bytes Ns = Ns Sy 160MB Pq ulong
448Max amount of memory to use for RAID-Z expansion I/O.
449This limits how much I/O can be outstanding at once.
450.
451.It Sy raidz_expand_max_reflow_bytes Ns = Ns Sy 0 Pq ulong
452For testing, pause RAID-Z expansion when reflow amount reaches this value.
453.
454.It Sy raidz_io_aggregate_rows Ns = Ns Sy 4 Pq ulong
455For expanded RAID-Z, aggregate reads that have more rows than this.
456.
457.It Sy reference_history Ns = Ns Sy 3 Pq int
458Maximum reference holders being tracked when reference_tracking_enable is
459active.
460.
461.It Sy reference_tracking_enable Ns = Ns Sy 0 Ns | Ns 1 Pq int
462Track reference holders to
463.Sy refcount_t
464objects (debug builds only).
465.
466.It Sy send_holes_without_birth_time Ns = Ns Sy 1 Ns | Ns 0 Pq int
467When set, the
468.Sy hole_birth
469optimization will not be used, and all holes will always be sent during a
470.Nm zfs Cm send .
471This is useful if you suspect your datasets are affected by a bug in
472.Sy hole_birth .
473.
474.It Sy spa_config_path Ns = Ns Pa /etc/zfs/zpool.cache Pq charp
475SPA config file.
476.
477.It Sy spa_asize_inflation Ns = Ns Sy 24 Pq uint
478Multiplication factor used to estimate actual disk consumption from the
479size of data being written.
480The default value is a worst case estimate,
481but lower values may be valid for a given pool depending on its configuration.
482Pool administrators who understand the factors involved
483may wish to specify a more realistic inflation factor,
484particularly if they operate close to quota or capacity limits.
485.
486.It Sy spa_load_print_vdev_tree Ns = Ns Sy 0 Ns | Ns 1 Pq int
487Whether to print the vdev tree in the debugging message buffer during pool
488import.
489.
490.It Sy spa_load_verify_data Ns = Ns Sy 1 Ns | Ns 0 Pq int
491Whether to traverse data blocks during an "extreme rewind"
492.Pq Fl X
493import.
494.Pp
495An extreme rewind import normally performs a full traversal of all
496blocks in the pool for verification.
497If this parameter is unset, the traversal skips non-metadata blocks.
498It can be toggled once the
499import has started to stop or start the traversal of non-metadata blocks.
500.
501.It Sy spa_load_verify_metadata  Ns = Ns Sy 1 Ns | Ns 0 Pq int
502Whether to traverse blocks during an "extreme rewind"
503.Pq Fl X
504pool import.
505.Pp
506An extreme rewind import normally performs a full traversal of all
507blocks in the pool for verification.
508If this parameter is unset, the traversal is not performed.
509It can be toggled once the import has started to stop or start the traversal.
510.
511.It Sy spa_load_verify_shift Ns = Ns Sy 4 Po 1/16th Pc Pq uint
512Sets the maximum number of bytes to consume during pool import to the log2
513fraction of the target ARC size.
514.
515.It Sy spa_slop_shift Ns = Ns Sy 5 Po 1/32nd Pc Pq int
516Normally, we don't allow the last
517.Sy 3.2% Pq Sy 1/2^spa_slop_shift
518of space in the pool to be consumed.
519This ensures that we don't run the pool completely out of space,
520due to unaccounted changes (e.g. to the MOS).
521It also limits the worst-case time to allocate space.
522If we have less than this amount of free space,
523most ZPL operations (e.g. write, create) will return
524.Sy ENOSPC .
525.
526.It Sy spa_num_allocators Ns = Ns Sy 4 Pq int
527Determines the number of block alloctators to use per spa instance.
528Capped by the number of actual CPUs in the system via
529.Sy spa_cpus_per_allocator .
530.Pp
531Note that setting this value too high could result in performance
532degredation and/or excess fragmentation.
533Set value only applies to pools imported/created after that.
534.
535.It Sy spa_cpus_per_allocator Ns = Ns Sy 4 Pq int
536Determines the minimum number of CPUs in a system for block alloctator
537per spa instance.
538Set value only applies to pools imported/created after that.
539.
540.It Sy spa_upgrade_errlog_limit Ns = Ns Sy 0 Pq uint
541Limits the number of on-disk error log entries that will be converted to the
542new format when enabling the
543.Sy head_errlog
544feature.
545The default is to convert all log entries.
546.
547.It Sy vdev_removal_max_span Ns = Ns Sy 32768 Ns B Po 32 KiB Pc Pq uint
548During top-level vdev removal, chunks of data are copied from the vdev
549which may include free space in order to trade bandwidth for IOPS.
550This parameter determines the maximum span of free space, in bytes,
551which will be included as "unnecessary" data in a chunk of copied data.
552.Pp
553The default value here was chosen to align with
554.Sy zfs_vdev_read_gap_limit ,
555which is a similar concept when doing
556regular reads (but there's no reason it has to be the same).
557.
558.It Sy vdev_file_logical_ashift Ns = Ns Sy 9 Po 512 B Pc Pq u64
559Logical ashift for file-based devices.
560.
561.It Sy vdev_file_physical_ashift Ns = Ns Sy 9 Po 512 B Pc Pq u64
562Physical ashift for file-based devices.
563.
564.It Sy zap_iterate_prefetch Ns = Ns Sy 1 Ns | Ns 0 Pq int
565If set, when we start iterating over a ZAP object,
566prefetch the entire object (all leaf blocks).
567However, this is limited by
568.Sy dmu_prefetch_max .
569.
570.It Sy zap_micro_max_size Ns = Ns Sy 131072 Ns B Po 128 KiB Pc Pq int
571Maximum micro ZAP size.
572A micro ZAP is upgraded to a fat ZAP, once it grows beyond the specified size.
573.
574.It Sy zap_shrink_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
575If set, adjacent empty ZAP blocks will be collapsed, reducing disk space.
576.
577.It Sy zfetch_min_distance Ns = Ns Sy 4194304 Ns B Po 4 MiB Pc Pq uint
578Min bytes to prefetch per stream.
579Prefetch distance starts from the demand access size and quickly grows to
580this value, doubling on each hit.
581After that it may grow further by 1/8 per hit, but only if some prefetch
582since last time haven't completed in time to satisfy demand request, i.e.
583prefetch depth didn't cover the read latency or the pool got saturated.
584.
585.It Sy zfetch_max_distance Ns = Ns Sy 67108864 Ns B Po 64 MiB Pc Pq uint
586Max bytes to prefetch per stream.
587.
588.It Sy zfetch_max_idistance Ns = Ns Sy 67108864 Ns B Po 64 MiB Pc Pq uint
589Max bytes to prefetch indirects for per stream.
590.
591.It Sy zfetch_max_reorder Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq uint
592Requests within this byte distance from the current prefetch stream position
593are considered parts of the stream, reordered due to parallel processing.
594Such requests do not advance the stream position immediately unless
595.Sy zfetch_hole_shift
596fill threshold is reached, but saved to fill holes in the stream later.
597.
598.It Sy zfetch_max_streams Ns = Ns Sy 8 Pq uint
599Max number of streams per zfetch (prefetch streams per file).
600.
601.It Sy zfetch_min_sec_reap Ns = Ns Sy 1 Pq uint
602Min time before inactive prefetch stream can be reclaimed
603.
604.It Sy zfetch_max_sec_reap Ns = Ns Sy 2 Pq uint
605Max time before inactive prefetch stream can be deleted
606.
607.It Sy zfs_abd_scatter_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
608Enables ARC from using scatter/gather lists and forces all allocations to be
609linear in kernel memory.
610Disabling can improve performance in some code paths
611at the expense of fragmented kernel memory.
612.
613.It Sy zfs_abd_scatter_max_order Ns = Ns Sy MAX_ORDER\-1 Pq uint
614Maximum number of consecutive memory pages allocated in a single block for
615scatter/gather lists.
616.Pp
617The value of
618.Sy MAX_ORDER
619depends on kernel configuration.
620.
621.It Sy zfs_abd_scatter_min_size Ns = Ns Sy 1536 Ns B Po 1.5 KiB Pc Pq uint
622This is the minimum allocation size that will use scatter (page-based) ABDs.
623Smaller allocations will use linear ABDs.
624.
625.It Sy zfs_arc_dnode_limit Ns = Ns Sy 0 Ns B Pq u64
626When the number of bytes consumed by dnodes in the ARC exceeds this number of
627bytes, try to unpin some of it in response to demand for non-metadata.
628This value acts as a ceiling to the amount of dnode metadata, and defaults to
629.Sy 0 ,
630which indicates that a percent which is based on
631.Sy zfs_arc_dnode_limit_percent
632of the ARC meta buffers that may be used for dnodes.
633.It Sy zfs_arc_dnode_limit_percent Ns = Ns Sy 10 Ns % Pq u64
634Percentage that can be consumed by dnodes of ARC meta buffers.
635.Pp
636See also
637.Sy zfs_arc_dnode_limit ,
638which serves a similar purpose but has a higher priority if nonzero.
639.
640.It Sy zfs_arc_dnode_reduce_percent Ns = Ns Sy 10 Ns % Pq u64
641Percentage of ARC dnodes to try to scan in response to demand for non-metadata
642when the number of bytes consumed by dnodes exceeds
643.Sy zfs_arc_dnode_limit .
644.
645.It Sy zfs_arc_average_blocksize Ns = Ns Sy 8192 Ns B Po 8 KiB Pc Pq uint
646The ARC's buffer hash table is sized based on the assumption of an average
647block size of this value.
648This works out to roughly 1 MiB of hash table per 1 GiB of physical memory
649with 8-byte pointers.
650For configurations with a known larger average block size,
651this value can be increased to reduce the memory footprint.
652.
653.It Sy zfs_arc_eviction_pct Ns = Ns Sy 200 Ns % Pq uint
654When
655.Fn arc_is_overflowing ,
656.Fn arc_get_data_impl
657waits for this percent of the requested amount of data to be evicted.
658For example, by default, for every
659.Em 2 KiB
660that's evicted,
661.Em 1 KiB
662of it may be "reused" by a new allocation.
663Since this is above
664.Sy 100 Ns % ,
665it ensures that progress is made towards getting
666.Sy arc_size No under Sy arc_c .
667Since this is finite, it ensures that allocations can still happen,
668even during the potentially long time that
669.Sy arc_size No is more than Sy arc_c .
670.
671.It Sy zfs_arc_evict_batch_limit Ns = Ns Sy 10 Pq uint
672Number ARC headers to evict per sub-list before proceeding to another sub-list.
673This batch-style operation prevents entire sub-lists from being evicted at once
674but comes at a cost of additional unlocking and locking.
675.
676.It Sy zfs_arc_grow_retry Ns = Ns Sy 0 Ns s Pq uint
677If set to a non zero value, it will replace the
678.Sy arc_grow_retry
679value with this value.
680The
681.Sy arc_grow_retry
682.No value Pq default Sy 5 Ns s
683is the number of seconds the ARC will wait before
684trying to resume growth after a memory pressure event.
685.
686.It Sy zfs_arc_lotsfree_percent Ns = Ns Sy 10 Ns % Pq int
687Throttle I/O when free system memory drops below this percentage of total
688system memory.
689Setting this value to
690.Sy 0
691will disable the throttle.
692.
693.It Sy zfs_arc_max Ns = Ns Sy 0 Ns B Pq u64
694Max size of ARC in bytes.
695If
696.Sy 0 ,
697then the max size of ARC is determined by the amount of system memory installed.
698The larger of
699.Sy all_system_memory No \- Sy 1 GiB
700and
701.Sy 5/8 No \(mu Sy all_system_memory
702will be used as the limit.
703This value must be at least
704.Sy 67108864 Ns B Pq 64 MiB .
705.Pp
706This value can be changed dynamically, with some caveats.
707It cannot be set back to
708.Sy 0
709while running, and reducing it below the current ARC size will not cause
710the ARC to shrink without memory pressure to induce shrinking.
711.
712.It Sy zfs_arc_meta_balance Ns = Ns Sy 500 Pq uint
713Balance between metadata and data on ghost hits.
714Values above 100 increase metadata caching by proportionally reducing effect
715of ghost data hits on target data/metadata rate.
716.
717.It Sy zfs_arc_min Ns = Ns Sy 0 Ns B Pq u64
718Min size of ARC in bytes.
719.No If set to Sy 0 , arc_c_min
720will default to consuming the larger of
721.Sy 32 MiB
722and
723.Sy all_system_memory No / Sy 32 .
724.
725.It Sy zfs_arc_min_prefetch_ms Ns = Ns Sy 0 Ns ms Ns Po Ns ≡ Ns 1s Pc Pq uint
726Minimum time prefetched blocks are locked in the ARC.
727.
728.It Sy zfs_arc_min_prescient_prefetch_ms Ns = Ns Sy 0 Ns ms Ns Po Ns ≡ Ns 6s Pc Pq uint
729Minimum time "prescient prefetched" blocks are locked in the ARC.
730These blocks are meant to be prefetched fairly aggressively ahead of
731the code that may use them.
732.
733.It Sy zfs_arc_prune_task_threads Ns = Ns Sy 1 Pq int
734Number of arc_prune threads.
735.Fx
736does not need more than one.
737Linux may theoretically use one per mount point up to number of CPUs,
738but that was not proven to be useful.
739.
740.It Sy zfs_max_missing_tvds Ns = Ns Sy 0 Pq int
741Number of missing top-level vdevs which will be allowed during
742pool import (only in read-only mode).
743.
744.It Sy zfs_max_nvlist_src_size Ns = Sy 0 Pq u64
745Maximum size in bytes allowed to be passed as
746.Sy zc_nvlist_src_size
747for ioctls on
748.Pa /dev/zfs .
749This prevents a user from causing the kernel to allocate
750an excessive amount of memory.
751When the limit is exceeded, the ioctl fails with
752.Sy EINVAL
753and a description of the error is sent to the
754.Pa zfs-dbgmsg
755log.
756This parameter should not need to be touched under normal circumstances.
757If
758.Sy 0 ,
759equivalent to a quarter of the user-wired memory limit under
760.Fx
761and to
762.Sy 134217728 Ns B Pq 128 MiB
763under Linux.
764.
765.It Sy zfs_multilist_num_sublists Ns = Ns Sy 0 Pq uint
766To allow more fine-grained locking, each ARC state contains a series
767of lists for both data and metadata objects.
768Locking is performed at the level of these "sub-lists".
769This parameters controls the number of sub-lists per ARC state,
770and also applies to other uses of the multilist data structure.
771.Pp
772If
773.Sy 0 ,
774equivalent to the greater of the number of online CPUs and
775.Sy 4 .
776.
777.It Sy zfs_arc_overflow_shift Ns = Ns Sy 8 Pq int
778The ARC size is considered to be overflowing if it exceeds the current
779ARC target size
780.Pq Sy arc_c
781by thresholds determined by this parameter.
782Exceeding by
783.Sy ( arc_c No >> Sy zfs_arc_overflow_shift ) No / Sy 2
784starts ARC reclamation process.
785If that appears insufficient, exceeding by
786.Sy ( arc_c No >> Sy zfs_arc_overflow_shift ) No \(mu Sy 1.5
787blocks new buffer allocation until the reclaim thread catches up.
788Started reclamation process continues till ARC size returns below the
789target size.
790.Pp
791The default value of
792.Sy 8
793causes the ARC to start reclamation if it exceeds the target size by
794.Em 0.2%
795of the target size, and block allocations by
796.Em 0.6% .
797.
798.It Sy zfs_arc_shrink_shift Ns = Ns Sy 0 Pq uint
799If nonzero, this will update
800.Sy arc_shrink_shift Pq default Sy 7
801with the new value.
802.
803.It Sy zfs_arc_pc_percent Ns = Ns Sy 0 Ns % Po off Pc Pq uint
804Percent of pagecache to reclaim ARC to.
805.Pp
806This tunable allows the ZFS ARC to play more nicely
807with the kernel's LRU pagecache.
808It can guarantee that the ARC size won't collapse under scanning
809pressure on the pagecache, yet still allows the ARC to be reclaimed down to
810.Sy zfs_arc_min
811if necessary.
812This value is specified as percent of pagecache size (as measured by
813.Sy NR_FILE_PAGES ) ,
814where that percent may exceed
815.Sy 100 .
816This
817only operates during memory pressure/reclaim.
818.
819.It Sy zfs_arc_shrinker_limit Ns = Ns Sy 10000 Pq int
820This is a limit on how many pages the ARC shrinker makes available for
821eviction in response to one page allocation attempt.
822Note that in practice, the kernel's shrinker can ask us to evict
823up to about four times this for one allocation attempt.
824.Pp
825The default limit of
826.Sy 10000 Pq in practice, Em 160 MiB No per allocation attempt with 4 KiB pages
827limits the amount of time spent attempting to reclaim ARC memory to
828less than 100 ms per allocation attempt,
829even with a small average compressed block size of ~8 KiB.
830.Pp
831The parameter can be set to 0 (zero) to disable the limit,
832and only applies on Linux.
833.
834.It Sy zfs_arc_sys_free Ns = Ns Sy 0 Ns B Pq u64
835The target number of bytes the ARC should leave as free memory on the system.
836If zero, equivalent to the bigger of
837.Sy 512 KiB No and Sy all_system_memory/64 .
838.
839.It Sy zfs_autoimport_disable Ns = Ns Sy 1 Ns | Ns 0 Pq int
840Disable pool import at module load by ignoring the cache file
841.Pq Sy spa_config_path .
842.
843.It Sy zfs_checksum_events_per_second Ns = Ns Sy 20 Ns /s Pq uint
844Rate limit checksum events to this many per second.
845Note that this should not be set below the ZED thresholds
846(currently 10 checksums over 10 seconds)
847or else the daemon may not trigger any action.
848.
849.It Sy zfs_commit_timeout_pct Ns = Ns Sy 10 Ns % Pq uint
850This controls the amount of time that a ZIL block (lwb) will remain "open"
851when it isn't "full", and it has a thread waiting for it to be committed to
852stable storage.
853The timeout is scaled based on a percentage of the last lwb
854latency to avoid significantly impacting the latency of each individual
855transaction record (itx).
856.
857.It Sy zfs_condense_indirect_commit_entry_delay_ms Ns = Ns Sy 0 Ns ms Pq int
858Vdev indirection layer (used for device removal) sleeps for this many
859milliseconds during mapping generation.
860Intended for use with the test suite to throttle vdev removal speed.
861.
862.It Sy zfs_condense_indirect_obsolete_pct Ns = Ns Sy 25 Ns % Pq uint
863Minimum percent of obsolete bytes in vdev mapping required to attempt to
864condense
865.Pq see Sy zfs_condense_indirect_vdevs_enable .
866Intended for use with the test suite
867to facilitate triggering condensing as needed.
868.
869.It Sy zfs_condense_indirect_vdevs_enable Ns = Ns Sy 1 Ns | Ns 0 Pq int
870Enable condensing indirect vdev mappings.
871When set, attempt to condense indirect vdev mappings
872if the mapping uses more than
873.Sy zfs_condense_min_mapping_bytes
874bytes of memory and if the obsolete space map object uses more than
875.Sy zfs_condense_max_obsolete_bytes
876bytes on-disk.
877The condensing process is an attempt to save memory by removing obsolete
878mappings.
879.
880.It Sy zfs_condense_max_obsolete_bytes Ns = Ns Sy 1073741824 Ns B Po 1 GiB Pc Pq u64
881Only attempt to condense indirect vdev mappings if the on-disk size
882of the obsolete space map object is greater than this number of bytes
883.Pq see Sy zfs_condense_indirect_vdevs_enable .
884.
885.It Sy zfs_condense_min_mapping_bytes Ns = Ns Sy 131072 Ns B Po 128 KiB Pc Pq u64
886Minimum size vdev mapping to attempt to condense
887.Pq see Sy zfs_condense_indirect_vdevs_enable .
888.
889.It Sy zfs_dbgmsg_enable Ns = Ns Sy 1 Ns | Ns 0 Pq int
890Internally ZFS keeps a small log to facilitate debugging.
891The log is enabled by default, and can be disabled by unsetting this option.
892The contents of the log can be accessed by reading
893.Pa /proc/spl/kstat/zfs/dbgmsg .
894Writing
895.Sy 0
896to the file clears the log.
897.Pp
898This setting does not influence debug prints due to
899.Sy zfs_flags .
900.
901.It Sy zfs_dbgmsg_maxsize Ns = Ns Sy 4194304 Ns B Po 4 MiB Pc Pq uint
902Maximum size of the internal ZFS debug log.
903.
904.It Sy zfs_dbuf_state_index Ns = Ns Sy 0 Pq int
905Historically used for controlling what reporting was available under
906.Pa /proc/spl/kstat/zfs .
907No effect.
908.
909.It Sy zfs_deadman_checktime_ms Ns = Ns Sy 60000 Ns ms Po 1 min Pc Pq u64
910Check time in milliseconds.
911This defines the frequency at which we check for hung I/O requests
912and potentially invoke the
913.Sy zfs_deadman_failmode
914behavior.
915.
916.It Sy zfs_deadman_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
917When a pool sync operation takes longer than
918.Sy zfs_deadman_synctime_ms ,
919or when an individual I/O operation takes longer than
920.Sy zfs_deadman_ziotime_ms ,
921then the operation is considered to be "hung".
922If
923.Sy zfs_deadman_enabled
924is set, then the deadman behavior is invoked as described by
925.Sy zfs_deadman_failmode .
926By default, the deadman is enabled and set to
927.Sy wait
928which results in "hung" I/O operations only being logged.
929The deadman is automatically disabled when a pool gets suspended.
930.
931.It Sy zfs_deadman_events_per_second Ns = Ns Sy 1 Ns /s Pq int
932Rate limit deadman zevents (which report hung I/O operations) to this many per
933second.
934.
935.It Sy zfs_deadman_failmode Ns = Ns Sy wait Pq charp
936Controls the failure behavior when the deadman detects a "hung" I/O operation.
937Valid values are:
938.Bl -tag -compact -offset 4n -width "continue"
939.It Sy wait
940Wait for a "hung" operation to complete.
941For each "hung" operation a "deadman" event will be posted
942describing that operation.
943.It Sy continue
944Attempt to recover from a "hung" operation by re-dispatching it
945to the I/O pipeline if possible.
946.It Sy panic
947Panic the system.
948This can be used to facilitate automatic fail-over
949to a properly configured fail-over partner.
950.El
951.
952.It Sy zfs_deadman_synctime_ms Ns = Ns Sy 600000 Ns ms Po 10 min Pc Pq u64
953Interval in milliseconds after which the deadman is triggered and also
954the interval after which a pool sync operation is considered to be "hung".
955Once this limit is exceeded the deadman will be invoked every
956.Sy zfs_deadman_checktime_ms
957milliseconds until the pool sync completes.
958.
959.It Sy zfs_deadman_ziotime_ms Ns = Ns Sy 300000 Ns ms Po 5 min Pc Pq u64
960Interval in milliseconds after which the deadman is triggered and an
961individual I/O operation is considered to be "hung".
962As long as the operation remains "hung",
963the deadman will be invoked every
964.Sy zfs_deadman_checktime_ms
965milliseconds until the operation completes.
966.
967.It Sy zfs_dedup_prefetch Ns = Ns Sy 0 Ns | Ns 1 Pq int
968Enable prefetching dedup-ed blocks which are going to be freed.
969.
970.It Sy zfs_delay_min_dirty_percent Ns = Ns Sy 60 Ns % Pq uint
971Start to delay each transaction once there is this amount of dirty data,
972expressed as a percentage of
973.Sy zfs_dirty_data_max .
974This value should be at least
975.Sy zfs_vdev_async_write_active_max_dirty_percent .
976.No See Sx ZFS TRANSACTION DELAY .
977.
978.It Sy zfs_delay_scale Ns = Ns Sy 500000 Pq int
979This controls how quickly the transaction delay approaches infinity.
980Larger values cause longer delays for a given amount of dirty data.
981.Pp
982For the smoothest delay, this value should be about 1 billion divided
983by the maximum number of operations per second.
984This will smoothly handle between ten times and a tenth of this number.
985.No See Sx ZFS TRANSACTION DELAY .
986.Pp
987.Sy zfs_delay_scale No \(mu Sy zfs_dirty_data_max Em must No be smaller than Sy 2^64 .
988.
989.It Sy zfs_disable_ivset_guid_check Ns = Ns Sy 0 Ns | Ns 1 Pq int
990Disables requirement for IVset GUIDs to be present and match when doing a raw
991receive of encrypted datasets.
992Intended for users whose pools were created with
993OpenZFS pre-release versions and now have compatibility issues.
994.
995.It Sy zfs_key_max_salt_uses Ns = Ns Sy 400000000 Po 4*10^8 Pc Pq ulong
996Maximum number of uses of a single salt value before generating a new one for
997encrypted datasets.
998The default value is also the maximum.
999.
1000.It Sy zfs_object_mutex_size Ns = Ns Sy 64 Pq uint
1001Size of the znode hashtable used for holds.
1002.Pp
1003Due to the need to hold locks on objects that may not exist yet, kernel mutexes
1004are not created per-object and instead a hashtable is used where collisions
1005will result in objects waiting when there is not actually contention on the
1006same object.
1007.
1008.It Sy zfs_slow_io_events_per_second Ns = Ns Sy 20 Ns /s Pq int
1009Rate limit delay zevents (which report slow I/O operations) to this many per
1010second.
1011.
1012.It Sy zfs_unflushed_max_mem_amt Ns = Ns Sy 1073741824 Ns B Po 1 GiB Pc Pq u64
1013Upper-bound limit for unflushed metadata changes to be held by the
1014log spacemap in memory, in bytes.
1015.
1016.It Sy zfs_unflushed_max_mem_ppm Ns = Ns Sy 1000 Ns ppm Po 0.1% Pc Pq u64
1017Part of overall system memory that ZFS allows to be used
1018for unflushed metadata changes by the log spacemap, in millionths.
1019.
1020.It Sy zfs_unflushed_log_block_max Ns = Ns Sy 131072 Po 128k Pc Pq u64
1021Describes the maximum number of log spacemap blocks allowed for each pool.
1022The default value means that the space in all the log spacemaps
1023can add up to no more than
1024.Sy 131072
1025blocks (which means
1026.Em 16 GiB
1027of logical space before compression and ditto blocks,
1028assuming that blocksize is
1029.Em 128 KiB ) .
1030.Pp
1031This tunable is important because it involves a trade-off between import
1032time after an unclean export and the frequency of flushing metaslabs.
1033The higher this number is, the more log blocks we allow when the pool is
1034active which means that we flush metaslabs less often and thus decrease
1035the number of I/O operations for spacemap updates per TXG.
1036At the same time though, that means that in the event of an unclean export,
1037there will be more log spacemap blocks for us to read, inducing overhead
1038in the import time of the pool.
1039The lower the number, the amount of flushing increases, destroying log
1040blocks quicker as they become obsolete faster, which leaves less blocks
1041to be read during import time after a crash.
1042.Pp
1043Each log spacemap block existing during pool import leads to approximately
1044one extra logical I/O issued.
1045This is the reason why this tunable is exposed in terms of blocks rather
1046than space used.
1047.
1048.It Sy zfs_unflushed_log_block_min Ns = Ns Sy 1000 Pq u64
1049If the number of metaslabs is small and our incoming rate is high,
1050we could get into a situation that we are flushing all our metaslabs every TXG.
1051Thus we always allow at least this many log blocks.
1052.
1053.It Sy zfs_unflushed_log_block_pct Ns = Ns Sy 400 Ns % Pq u64
1054Tunable used to determine the number of blocks that can be used for
1055the spacemap log, expressed as a percentage of the total number of
1056unflushed metaslabs in the pool.
1057.
1058.It Sy zfs_unflushed_log_txg_max Ns = Ns Sy 1000 Pq u64
1059Tunable limiting maximum time in TXGs any metaslab may remain unflushed.
1060It effectively limits maximum number of unflushed per-TXG spacemap logs
1061that need to be read after unclean pool export.
1062.
1063.It Sy zfs_unlink_suspend_progress Ns = Ns Sy 0 Ns | Ns 1 Pq uint
1064When enabled, files will not be asynchronously removed from the list of pending
1065unlinks and the space they consume will be leaked.
1066Once this option has been disabled and the dataset is remounted,
1067the pending unlinks will be processed and the freed space returned to the pool.
1068This option is used by the test suite.
1069.
1070.It Sy zfs_delete_blocks Ns = Ns Sy 20480 Pq ulong
1071This is the used to define a large file for the purposes of deletion.
1072Files containing more than
1073.Sy zfs_delete_blocks
1074will be deleted asynchronously, while smaller files are deleted synchronously.
1075Decreasing this value will reduce the time spent in an
1076.Xr unlink 2
1077system call, at the expense of a longer delay before the freed space is
1078available.
1079This only applies on Linux.
1080.
1081.It Sy zfs_dirty_data_max Ns = Pq int
1082Determines the dirty space limit in bytes.
1083Once this limit is exceeded, new writes are halted until space frees up.
1084This parameter takes precedence over
1085.Sy zfs_dirty_data_max_percent .
1086.No See Sx ZFS TRANSACTION DELAY .
1087.Pp
1088Defaults to
1089.Sy physical_ram/10 ,
1090capped at
1091.Sy zfs_dirty_data_max_max .
1092.
1093.It Sy zfs_dirty_data_max_max Ns = Pq int
1094Maximum allowable value of
1095.Sy zfs_dirty_data_max ,
1096expressed in bytes.
1097This limit is only enforced at module load time, and will be ignored if
1098.Sy zfs_dirty_data_max
1099is later changed.
1100This parameter takes precedence over
1101.Sy zfs_dirty_data_max_max_percent .
1102.No See Sx ZFS TRANSACTION DELAY .
1103.Pp
1104Defaults to
1105.Sy min(physical_ram/4, 4GiB) ,
1106or
1107.Sy min(physical_ram/4, 1GiB)
1108for 32-bit systems.
1109.
1110.It Sy zfs_dirty_data_max_max_percent Ns = Ns Sy 25 Ns % Pq uint
1111Maximum allowable value of
1112.Sy zfs_dirty_data_max ,
1113expressed as a percentage of physical RAM.
1114This limit is only enforced at module load time, and will be ignored if
1115.Sy zfs_dirty_data_max
1116is later changed.
1117The parameter
1118.Sy zfs_dirty_data_max_max
1119takes precedence over this one.
1120.No See Sx ZFS TRANSACTION DELAY .
1121.
1122.It Sy zfs_dirty_data_max_percent Ns = Ns Sy 10 Ns % Pq uint
1123Determines the dirty space limit, expressed as a percentage of all memory.
1124Once this limit is exceeded, new writes are halted until space frees up.
1125The parameter
1126.Sy zfs_dirty_data_max
1127takes precedence over this one.
1128.No See Sx ZFS TRANSACTION DELAY .
1129.Pp
1130Subject to
1131.Sy zfs_dirty_data_max_max .
1132.
1133.It Sy zfs_dirty_data_sync_percent Ns = Ns Sy 20 Ns % Pq uint
1134Start syncing out a transaction group if there's at least this much dirty data
1135.Pq as a percentage of Sy zfs_dirty_data_max .
1136This should be less than
1137.Sy zfs_vdev_async_write_active_min_dirty_percent .
1138.
1139.It Sy zfs_wrlog_data_max Ns = Pq int
1140The upper limit of write-transaction zil log data size in bytes.
1141Write operations are throttled when approaching the limit until log data is
1142cleared out after transaction group sync.
1143Because of some overhead, it should be set at least 2 times the size of
1144.Sy zfs_dirty_data_max
1145.No to prevent harming normal write throughput .
1146It also should be smaller than the size of the slog device if slog is present.
1147.Pp
1148Defaults to
1149.Sy zfs_dirty_data_max*2
1150.
1151.It Sy zfs_fallocate_reserve_percent Ns = Ns Sy 110 Ns % Pq uint
1152Since ZFS is a copy-on-write filesystem with snapshots, blocks cannot be
1153preallocated for a file in order to guarantee that later writes will not
1154run out of space.
1155Instead,
1156.Xr fallocate 2
1157space preallocation only checks that sufficient space is currently available
1158in the pool or the user's project quota allocation,
1159and then creates a sparse file of the requested size.
1160The requested space is multiplied by
1161.Sy zfs_fallocate_reserve_percent
1162to allow additional space for indirect blocks and other internal metadata.
1163Setting this to
1164.Sy 0
1165disables support for
1166.Xr fallocate 2
1167and causes it to return
1168.Sy EOPNOTSUPP .
1169.
1170.It Sy zfs_fletcher_4_impl Ns = Ns Sy fastest Pq string
1171Select a fletcher 4 implementation.
1172.Pp
1173Supported selectors are:
1174.Sy fastest , scalar , sse2 , ssse3 , avx2 , avx512f , avx512bw ,
1175.No and Sy aarch64_neon .
1176All except
1177.Sy fastest No and Sy scalar
1178require instruction set extensions to be available,
1179and will only appear if ZFS detects that they are present at runtime.
1180If multiple implementations of fletcher 4 are available, the
1181.Sy fastest
1182will be chosen using a micro benchmark.
1183Selecting
1184.Sy scalar
1185results in the original CPU-based calculation being used.
1186Selecting any option other than
1187.Sy fastest No or Sy scalar
1188results in vector instructions
1189from the respective CPU instruction set being used.
1190.
1191.It Sy zfs_bclone_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
1192Enable the experimental block cloning feature.
1193If this setting is 0, then even if feature@block_cloning is enabled,
1194attempts to clone blocks will act as though the feature is disabled.
1195.
1196.It Sy zfs_bclone_wait_dirty Ns = Ns Sy 0 Ns | Ns 1 Pq int
1197When set to 1 the FICLONE and FICLONERANGE ioctls wait for dirty data to be
1198written to disk.
1199This allows the clone operation to reliably succeed when a file is
1200modified and then immediately cloned.
1201For small files this may be slower than making a copy of the file.
1202Therefore, this setting defaults to 0 which causes a clone operation to
1203immediately fail when encountering a dirty block.
1204.
1205.It Sy zfs_blake3_impl Ns = Ns Sy fastest Pq string
1206Select a BLAKE3 implementation.
1207.Pp
1208Supported selectors are:
1209.Sy cycle , fastest , generic , sse2 , sse41 , avx2 , avx512 .
1210All except
1211.Sy cycle , fastest No and Sy generic
1212require instruction set extensions to be available,
1213and will only appear if ZFS detects that they are present at runtime.
1214If multiple implementations of BLAKE3 are available, the
1215.Sy fastest will be chosen using a micro benchmark. You can see the
1216benchmark results by reading this kstat file:
1217.Pa /proc/spl/kstat/zfs/chksum_bench .
1218.
1219.It Sy zfs_free_bpobj_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
1220Enable/disable the processing of the free_bpobj object.
1221.
1222.It Sy zfs_async_block_max_blocks Ns = Ns Sy UINT64_MAX Po unlimited Pc Pq u64
1223Maximum number of blocks freed in a single TXG.
1224.
1225.It Sy zfs_max_async_dedup_frees Ns = Ns Sy 100000 Po 10^5 Pc Pq u64
1226Maximum number of dedup blocks freed in a single TXG.
1227.
1228.It Sy zfs_vdev_async_read_max_active Ns = Ns Sy 3 Pq uint
1229Maximum asynchronous read I/O operations active to each device.
1230.No See Sx ZFS I/O SCHEDULER .
1231.
1232.It Sy zfs_vdev_async_read_min_active Ns = Ns Sy 1 Pq uint
1233Minimum asynchronous read I/O operation active to each device.
1234.No See Sx ZFS I/O SCHEDULER .
1235.
1236.It Sy zfs_vdev_async_write_active_max_dirty_percent Ns = Ns Sy 60 Ns % Pq uint
1237When the pool has more than this much dirty data, use
1238.Sy zfs_vdev_async_write_max_active
1239to limit active async writes.
1240If the dirty data is between the minimum and maximum,
1241the active I/O limit is linearly interpolated.
1242.No See Sx ZFS I/O SCHEDULER .
1243.
1244.It Sy zfs_vdev_async_write_active_min_dirty_percent Ns = Ns Sy 30 Ns % Pq uint
1245When the pool has less than this much dirty data, use
1246.Sy zfs_vdev_async_write_min_active
1247to limit active async writes.
1248If the dirty data is between the minimum and maximum,
1249the active I/O limit is linearly
1250interpolated.
1251.No See Sx ZFS I/O SCHEDULER .
1252.
1253.It Sy zfs_vdev_async_write_max_active Ns = Ns Sy 10 Pq uint
1254Maximum asynchronous write I/O operations active to each device.
1255.No See Sx ZFS I/O SCHEDULER .
1256.
1257.It Sy zfs_vdev_async_write_min_active Ns = Ns Sy 2 Pq uint
1258Minimum asynchronous write I/O operations active to each device.
1259.No See Sx ZFS I/O SCHEDULER .
1260.Pp
1261Lower values are associated with better latency on rotational media but poorer
1262resilver performance.
1263The default value of
1264.Sy 2
1265was chosen as a compromise.
1266A value of
1267.Sy 3
1268has been shown to improve resilver performance further at a cost of
1269further increasing latency.
1270.
1271.It Sy zfs_vdev_initializing_max_active Ns = Ns Sy 1 Pq uint
1272Maximum initializing I/O operations active to each device.
1273.No See Sx ZFS I/O SCHEDULER .
1274.
1275.It Sy zfs_vdev_initializing_min_active Ns = Ns Sy 1 Pq uint
1276Minimum initializing I/O operations active to each device.
1277.No See Sx ZFS I/O SCHEDULER .
1278.
1279.It Sy zfs_vdev_max_active Ns = Ns Sy 1000 Pq uint
1280The maximum number of I/O operations active to each device.
1281Ideally, this will be at least the sum of each queue's
1282.Sy max_active .
1283.No See Sx ZFS I/O SCHEDULER .
1284.
1285.It Sy zfs_vdev_open_timeout_ms Ns = Ns Sy 1000 Pq uint
1286Timeout value to wait before determining a device is missing
1287during import.
1288This is helpful for transient missing paths due
1289to links being briefly removed and recreated in response to
1290udev events.
1291.
1292.It Sy zfs_vdev_rebuild_max_active Ns = Ns Sy 3 Pq uint
1293Maximum sequential resilver I/O operations active to each device.
1294.No See Sx ZFS I/O SCHEDULER .
1295.
1296.It Sy zfs_vdev_rebuild_min_active Ns = Ns Sy 1 Pq uint
1297Minimum sequential resilver I/O operations active to each device.
1298.No See Sx ZFS I/O SCHEDULER .
1299.
1300.It Sy zfs_vdev_removal_max_active Ns = Ns Sy 2 Pq uint
1301Maximum removal I/O operations active to each device.
1302.No See Sx ZFS I/O SCHEDULER .
1303.
1304.It Sy zfs_vdev_removal_min_active Ns = Ns Sy 1 Pq uint
1305Minimum removal I/O operations active to each device.
1306.No See Sx ZFS I/O SCHEDULER .
1307.
1308.It Sy zfs_vdev_scrub_max_active Ns = Ns Sy 2 Pq uint
1309Maximum scrub I/O operations active to each device.
1310.No See Sx ZFS I/O SCHEDULER .
1311.
1312.It Sy zfs_vdev_scrub_min_active Ns = Ns Sy 1 Pq uint
1313Minimum scrub I/O operations active to each device.
1314.No See Sx ZFS I/O SCHEDULER .
1315.
1316.It Sy zfs_vdev_sync_read_max_active Ns = Ns Sy 10 Pq uint
1317Maximum synchronous read I/O operations active to each device.
1318.No See Sx ZFS I/O SCHEDULER .
1319.
1320.It Sy zfs_vdev_sync_read_min_active Ns = Ns Sy 10 Pq uint
1321Minimum synchronous read I/O operations active to each device.
1322.No See Sx ZFS I/O SCHEDULER .
1323.
1324.It Sy zfs_vdev_sync_write_max_active Ns = Ns Sy 10 Pq uint
1325Maximum synchronous write I/O operations active to each device.
1326.No See Sx ZFS I/O SCHEDULER .
1327.
1328.It Sy zfs_vdev_sync_write_min_active Ns = Ns Sy 10 Pq uint
1329Minimum synchronous write I/O operations active to each device.
1330.No See Sx ZFS I/O SCHEDULER .
1331.
1332.It Sy zfs_vdev_trim_max_active Ns = Ns Sy 2 Pq uint
1333Maximum trim/discard I/O operations active to each device.
1334.No See Sx ZFS I/O SCHEDULER .
1335.
1336.It Sy zfs_vdev_trim_min_active Ns = Ns Sy 1 Pq uint
1337Minimum trim/discard I/O operations active to each device.
1338.No See Sx ZFS I/O SCHEDULER .
1339.
1340.It Sy zfs_vdev_nia_delay Ns = Ns Sy 5 Pq uint
1341For non-interactive I/O (scrub, resilver, removal, initialize and rebuild),
1342the number of concurrently-active I/O operations is limited to
1343.Sy zfs_*_min_active ,
1344unless the vdev is "idle".
1345When there are no interactive I/O operations active (synchronous or otherwise),
1346and
1347.Sy zfs_vdev_nia_delay
1348operations have completed since the last interactive operation,
1349then the vdev is considered to be "idle",
1350and the number of concurrently-active non-interactive operations is increased to
1351.Sy zfs_*_max_active .
1352.No See Sx ZFS I/O SCHEDULER .
1353.
1354.It Sy zfs_vdev_nia_credit Ns = Ns Sy 5 Pq uint
1355Some HDDs tend to prioritize sequential I/O so strongly, that concurrent
1356random I/O latency reaches several seconds.
1357On some HDDs this happens even if sequential I/O operations
1358are submitted one at a time, and so setting
1359.Sy zfs_*_max_active Ns = Sy 1
1360does not help.
1361To prevent non-interactive I/O, like scrub,
1362from monopolizing the device, no more than
1363.Sy zfs_vdev_nia_credit operations can be sent
1364while there are outstanding incomplete interactive operations.
1365This enforced wait ensures the HDD services the interactive I/O
1366within a reasonable amount of time.
1367.No See Sx ZFS I/O SCHEDULER .
1368.
1369.It Sy zfs_vdev_queue_depth_pct Ns = Ns Sy 1000 Ns % Pq uint
1370Maximum number of queued allocations per top-level vdev expressed as
1371a percentage of
1372.Sy zfs_vdev_async_write_max_active ,
1373which allows the system to detect devices that are more capable
1374of handling allocations and to allocate more blocks to those devices.
1375This allows for dynamic allocation distribution when devices are imbalanced,
1376as fuller devices will tend to be slower than empty devices.
1377.Pp
1378Also see
1379.Sy zio_dva_throttle_enabled .
1380.
1381.It Sy zfs_vdev_def_queue_depth Ns = Ns Sy 32 Pq uint
1382Default queue depth for each vdev IO allocator.
1383Higher values allow for better coalescing of sequential writes before sending
1384them to the disk, but can increase transaction commit times.
1385.
1386.It Sy zfs_vdev_failfast_mask Ns = Ns Sy 1 Pq uint
1387Defines if the driver should retire on a given error type.
1388The following options may be bitwise-ored together:
1389.TS
1390box;
1391lbz r l l .
1392	Value	Name	Description
1393_
1394	1	Device	No driver retries on device errors
1395	2	Transport	No driver retries on transport errors.
1396	4	Driver	No driver retries on driver errors.
1397.TE
1398.
1399.It Sy zfs_vdev_disk_max_segs Ns = Ns Sy 0 Pq uint
1400Maximum number of segments to add to a BIO (min 4).
1401If this is higher than the maximum allowed by the device queue or the kernel
1402itself, it will be clamped.
1403Setting it to zero will cause the kernel's ideal size to be used.
1404This parameter only applies on Linux.
1405This parameter is ignored if
1406.Sy zfs_vdev_disk_classic Ns = Ns Sy 1 .
1407.
1408.It Sy zfs_vdev_disk_classic Ns = Ns Sy 0 Ns | Ns 1 Pq uint
1409If set to 1, OpenZFS will submit IO to Linux using the method it used in 2.2
1410and earlier.
1411This "classic" method has known issues with highly fragmented IO requests and
1412is slower on many workloads, but it has been in use for many years and is known
1413to be very stable.
1414If you set this parameter, please also open a bug report why you did so,
1415including the workload involved and any error messages.
1416.Pp
1417This parameter and the classic submission method will be removed once we have
1418total confidence in the new method.
1419.Pp
1420This parameter only applies on Linux, and can only be set at module load time.
1421.
1422.It Sy zfs_expire_snapshot Ns = Ns Sy 300 Ns s Pq int
1423Time before expiring
1424.Pa .zfs/snapshot .
1425.
1426.It Sy zfs_admin_snapshot Ns = Ns Sy 0 Ns | Ns 1 Pq int
1427Allow the creation, removal, or renaming of entries in the
1428.Sy .zfs/snapshot
1429directory to cause the creation, destruction, or renaming of snapshots.
1430When enabled, this functionality works both locally and over NFS exports
1431which have the
1432.Em no_root_squash
1433option set.
1434.
1435.It Sy zfs_flags Ns = Ns Sy 0 Pq int
1436Set additional debugging flags.
1437The following flags may be bitwise-ored together:
1438.TS
1439box;
1440lbz r l l .
1441	Value	Name	Description
1442_
1443	1	ZFS_DEBUG_DPRINTF	Enable dprintf entries in the debug log.
1444*	2	ZFS_DEBUG_DBUF_VERIFY	Enable extra dbuf verifications.
1445*	4	ZFS_DEBUG_DNODE_VERIFY	Enable extra dnode verifications.
1446	8	ZFS_DEBUG_SNAPNAMES	Enable snapshot name verification.
1447*	16	ZFS_DEBUG_MODIFY	Check for illegally modified ARC buffers.
1448	64	ZFS_DEBUG_ZIO_FREE	Enable verification of block frees.
1449	128	ZFS_DEBUG_HISTOGRAM_VERIFY	Enable extra spacemap histogram verifications.
1450	256	ZFS_DEBUG_METASLAB_VERIFY	Verify space accounting on disk matches in-memory \fBrange_trees\fP.
1451	512	ZFS_DEBUG_SET_ERROR	Enable \fBSET_ERROR\fP and dprintf entries in the debug log.
1452	1024	ZFS_DEBUG_INDIRECT_REMAP	Verify split blocks created by device removal.
1453	2048	ZFS_DEBUG_TRIM	Verify TRIM ranges are always within the allocatable range tree.
1454	4096	ZFS_DEBUG_LOG_SPACEMAP	Verify that the log summary is consistent with the spacemap log
1455			       and enable \fBzfs_dbgmsgs\fP for metaslab loading and flushing.
1456.TE
1457.Sy \& * No Requires debug build .
1458.
1459.It Sy zfs_btree_verify_intensity Ns = Ns Sy 0 Pq uint
1460Enables btree verification.
1461The following settings are culminative:
1462.TS
1463box;
1464lbz r l l .
1465	Value	Description
1466
1467	1	Verify height.
1468	2	Verify pointers from children to parent.
1469	3	Verify element counts.
1470	4	Verify element order. (expensive)
1471*	5	Verify unused memory is poisoned. (expensive)
1472.TE
1473.Sy \& * No Requires debug build .
1474.
1475.It Sy zfs_free_leak_on_eio Ns = Ns Sy 0 Ns | Ns 1 Pq int
1476If destroy encounters an
1477.Sy EIO
1478while reading metadata (e.g. indirect blocks),
1479space referenced by the missing metadata can not be freed.
1480Normally this causes the background destroy to become "stalled",
1481as it is unable to make forward progress.
1482While in this stalled state, all remaining space to free
1483from the error-encountering filesystem is "temporarily leaked".
1484Set this flag to cause it to ignore the
1485.Sy EIO ,
1486permanently leak the space from indirect blocks that can not be read,
1487and continue to free everything else that it can.
1488.Pp
1489The default "stalling" behavior is useful if the storage partially
1490fails (i.e. some but not all I/O operations fail), and then later recovers.
1491In this case, we will be able to continue pool operations while it is
1492partially failed, and when it recovers, we can continue to free the
1493space, with no leaks.
1494Note, however, that this case is actually fairly rare.
1495.Pp
1496Typically pools either
1497.Bl -enum -compact -offset 4n -width "1."
1498.It
1499fail completely (but perhaps temporarily,
1500e.g. due to a top-level vdev going offline), or
1501.It
1502have localized, permanent errors (e.g. disk returns the wrong data
1503due to bit flip or firmware bug).
1504.El
1505In the former case, this setting does not matter because the
1506pool will be suspended and the sync thread will not be able to make
1507forward progress regardless.
1508In the latter, because the error is permanent, the best we can do
1509is leak the minimum amount of space,
1510which is what setting this flag will do.
1511It is therefore reasonable for this flag to normally be set,
1512but we chose the more conservative approach of not setting it,
1513so that there is no possibility of
1514leaking space in the "partial temporary" failure case.
1515.
1516.It Sy zfs_free_min_time_ms Ns = Ns Sy 1000 Ns ms Po 1s Pc Pq uint
1517During a
1518.Nm zfs Cm destroy
1519operation using the
1520.Sy async_destroy
1521feature,
1522a minimum of this much time will be spent working on freeing blocks per TXG.
1523.
1524.It Sy zfs_obsolete_min_time_ms Ns = Ns Sy 500 Ns ms Pq uint
1525Similar to
1526.Sy zfs_free_min_time_ms ,
1527but for cleanup of old indirection records for removed vdevs.
1528.
1529.It Sy zfs_immediate_write_sz Ns = Ns Sy 32768 Ns B Po 32 KiB Pc Pq s64
1530Largest data block to write to the ZIL.
1531Larger blocks will be treated as if the dataset being written to had the
1532.Sy logbias Ns = Ns Sy throughput
1533property set.
1534.
1535.It Sy zfs_initialize_value Ns = Ns Sy 16045690984833335022 Po 0xDEADBEEFDEADBEEE Pc Pq u64
1536Pattern written to vdev free space by
1537.Xr zpool-initialize 8 .
1538.
1539.It Sy zfs_initialize_chunk_size Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq u64
1540Size of writes used by
1541.Xr zpool-initialize 8 .
1542This option is used by the test suite.
1543.
1544.It Sy zfs_livelist_max_entries Ns = Ns Sy 500000 Po 5*10^5 Pc Pq u64
1545The threshold size (in block pointers) at which we create a new sub-livelist.
1546Larger sublists are more costly from a memory perspective but the fewer
1547sublists there are, the lower the cost of insertion.
1548.
1549.It Sy zfs_livelist_min_percent_shared Ns = Ns Sy 75 Ns % Pq int
1550If the amount of shared space between a snapshot and its clone drops below
1551this threshold, the clone turns off the livelist and reverts to the old
1552deletion method.
1553This is in place because livelists no long give us a benefit
1554once a clone has been overwritten enough.
1555.
1556.It Sy zfs_livelist_condense_new_alloc Ns = Ns Sy 0 Pq int
1557Incremented each time an extra ALLOC blkptr is added to a livelist entry while
1558it is being condensed.
1559This option is used by the test suite to track race conditions.
1560.
1561.It Sy zfs_livelist_condense_sync_cancel Ns = Ns Sy 0 Pq int
1562Incremented each time livelist condensing is canceled while in
1563.Fn spa_livelist_condense_sync .
1564This option is used by the test suite to track race conditions.
1565.
1566.It Sy zfs_livelist_condense_sync_pause Ns = Ns Sy 0 Ns | Ns 1 Pq int
1567When set, the livelist condense process pauses indefinitely before
1568executing the synctask \(em
1569.Fn spa_livelist_condense_sync .
1570This option is used by the test suite to trigger race conditions.
1571.
1572.It Sy zfs_livelist_condense_zthr_cancel Ns = Ns Sy 0 Pq int
1573Incremented each time livelist condensing is canceled while in
1574.Fn spa_livelist_condense_cb .
1575This option is used by the test suite to track race conditions.
1576.
1577.It Sy zfs_livelist_condense_zthr_pause Ns = Ns Sy 0 Ns | Ns 1 Pq int
1578When set, the livelist condense process pauses indefinitely before
1579executing the open context condensing work in
1580.Fn spa_livelist_condense_cb .
1581This option is used by the test suite to trigger race conditions.
1582.
1583.It Sy zfs_lua_max_instrlimit Ns = Ns Sy 100000000 Po 10^8 Pc Pq u64
1584The maximum execution time limit that can be set for a ZFS channel program,
1585specified as a number of Lua instructions.
1586.
1587.It Sy zfs_lua_max_memlimit Ns = Ns Sy 104857600 Po 100 MiB Pc Pq u64
1588The maximum memory limit that can be set for a ZFS channel program, specified
1589in bytes.
1590.
1591.It Sy zfs_max_dataset_nesting Ns = Ns Sy 50 Pq int
1592The maximum depth of nested datasets.
1593This value can be tuned temporarily to
1594fix existing datasets that exceed the predefined limit.
1595.
1596.It Sy zfs_max_log_walking Ns = Ns Sy 5 Pq u64
1597The number of past TXGs that the flushing algorithm of the log spacemap
1598feature uses to estimate incoming log blocks.
1599.
1600.It Sy zfs_max_logsm_summary_length Ns = Ns Sy 10 Pq u64
1601Maximum number of rows allowed in the summary of the spacemap log.
1602.
1603.It Sy zfs_max_recordsize Ns = Ns Sy 16777216 Po 16 MiB Pc Pq uint
1604We currently support block sizes from
1605.Em 512 Po 512 B Pc No to Em 16777216 Po 16 MiB Pc .
1606The benefits of larger blocks, and thus larger I/O,
1607need to be weighed against the cost of COWing a giant block to modify one byte.
1608Additionally, very large blocks can have an impact on I/O latency,
1609and also potentially on the memory allocator.
1610Therefore, we formerly forbade creating blocks larger than 1M.
1611Larger blocks could be created by changing it,
1612and pools with larger blocks can always be imported and used,
1613regardless of this setting.
1614.
1615.It Sy zfs_allow_redacted_dataset_mount Ns = Ns Sy 0 Ns | Ns 1 Pq int
1616Allow datasets received with redacted send/receive to be mounted.
1617Normally disabled because these datasets may be missing key data.
1618.
1619.It Sy zfs_min_metaslabs_to_flush Ns = Ns Sy 1 Pq u64
1620Minimum number of metaslabs to flush per dirty TXG.
1621.
1622.It Sy zfs_metaslab_fragmentation_threshold Ns = Ns Sy 70 Ns % Pq uint
1623Allow metaslabs to keep their active state as long as their fragmentation
1624percentage is no more than this value.
1625An active metaslab that exceeds this threshold
1626will no longer keep its active status allowing better metaslabs to be selected.
1627.
1628.It Sy zfs_mg_fragmentation_threshold Ns = Ns Sy 95 Ns % Pq uint
1629Metaslab groups are considered eligible for allocations if their
1630fragmentation metric (measured as a percentage) is less than or equal to
1631this value.
1632If a metaslab group exceeds this threshold then it will be
1633skipped unless all metaslab groups within the metaslab class have also
1634crossed this threshold.
1635.
1636.It Sy zfs_mg_noalloc_threshold Ns = Ns Sy 0 Ns % Pq uint
1637Defines a threshold at which metaslab groups should be eligible for allocations.
1638The value is expressed as a percentage of free space
1639beyond which a metaslab group is always eligible for allocations.
1640If a metaslab group's free space is less than or equal to the
1641threshold, the allocator will avoid allocating to that group
1642unless all groups in the pool have reached the threshold.
1643Once all groups have reached the threshold, all groups are allowed to accept
1644allocations.
1645The default value of
1646.Sy 0
1647disables the feature and causes all metaslab groups to be eligible for
1648allocations.
1649.Pp
1650This parameter allows one to deal with pools having heavily imbalanced
1651vdevs such as would be the case when a new vdev has been added.
1652Setting the threshold to a non-zero percentage will stop allocations
1653from being made to vdevs that aren't filled to the specified percentage
1654and allow lesser filled vdevs to acquire more allocations than they
1655otherwise would under the old
1656.Sy zfs_mg_alloc_failures
1657facility.
1658.
1659.It Sy zfs_ddt_data_is_special Ns = Ns Sy 1 Ns | Ns 0 Pq int
1660If enabled, ZFS will place DDT data into the special allocation class.
1661.
1662.It Sy zfs_user_indirect_is_special Ns = Ns Sy 1 Ns | Ns 0 Pq int
1663If enabled, ZFS will place user data indirect blocks
1664into the special allocation class.
1665.
1666.It Sy zfs_multihost_history Ns = Ns Sy 0 Pq uint
1667Historical statistics for this many latest multihost updates will be available
1668in
1669.Pa /proc/spl/kstat/zfs/ Ns Ao Ar pool Ac Ns Pa /multihost .
1670.
1671.It Sy zfs_multihost_interval Ns = Ns Sy 1000 Ns ms Po 1 s Pc Pq u64
1672Used to control the frequency of multihost writes which are performed when the
1673.Sy multihost
1674pool property is on.
1675This is one of the factors used to determine the
1676length of the activity check during import.
1677.Pp
1678The multihost write period is
1679.Sy zfs_multihost_interval No / Sy leaf-vdevs .
1680On average a multihost write will be issued for each leaf vdev
1681every
1682.Sy zfs_multihost_interval
1683milliseconds.
1684In practice, the observed period can vary with the I/O load
1685and this observed value is the delay which is stored in the uberblock.
1686.
1687.It Sy zfs_multihost_import_intervals Ns = Ns Sy 20 Pq uint
1688Used to control the duration of the activity test on import.
1689Smaller values of
1690.Sy zfs_multihost_import_intervals
1691will reduce the import time but increase
1692the risk of failing to detect an active pool.
1693The total activity check time is never allowed to drop below one second.
1694.Pp
1695On import the activity check waits a minimum amount of time determined by
1696.Sy zfs_multihost_interval No \(mu Sy zfs_multihost_import_intervals ,
1697or the same product computed on the host which last had the pool imported,
1698whichever is greater.
1699The activity check time may be further extended if the value of MMP
1700delay found in the best uberblock indicates actual multihost updates happened
1701at longer intervals than
1702.Sy zfs_multihost_interval .
1703A minimum of
1704.Em 100 ms
1705is enforced.
1706.Pp
1707.Sy 0 No is equivalent to Sy 1 .
1708.
1709.It Sy zfs_multihost_fail_intervals Ns = Ns Sy 10 Pq uint
1710Controls the behavior of the pool when multihost write failures or delays are
1711detected.
1712.Pp
1713When
1714.Sy 0 ,
1715multihost write failures or delays are ignored.
1716The failures will still be reported to the ZED which depending on
1717its configuration may take action such as suspending the pool or offlining a
1718device.
1719.Pp
1720Otherwise, the pool will be suspended if
1721.Sy zfs_multihost_fail_intervals No \(mu Sy zfs_multihost_interval
1722milliseconds pass without a successful MMP write.
1723This guarantees the activity test will see MMP writes if the pool is imported.
1724.Sy 1 No is equivalent to Sy 2 ;
1725this is necessary to prevent the pool from being suspended
1726due to normal, small I/O latency variations.
1727.
1728.It Sy zfs_no_scrub_io Ns = Ns Sy 0 Ns | Ns 1 Pq int
1729Set to disable scrub I/O.
1730This results in scrubs not actually scrubbing data and
1731simply doing a metadata crawl of the pool instead.
1732.
1733.It Sy zfs_no_scrub_prefetch Ns = Ns Sy 0 Ns | Ns 1 Pq int
1734Set to disable block prefetching for scrubs.
1735.
1736.It Sy zfs_nocacheflush Ns = Ns Sy 0 Ns | Ns 1 Pq int
1737Disable cache flush operations on disks when writing.
1738Setting this will cause pool corruption on power loss
1739if a volatile out-of-order write cache is enabled.
1740.
1741.It Sy zfs_nopwrite_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
1742Allow no-operation writes.
1743The occurrence of nopwrites will further depend on other pool properties
1744.Pq i.a. the checksumming and compression algorithms .
1745.
1746.It Sy zfs_dmu_offset_next_sync Ns = Ns Sy 1 Ns | Ns 0 Pq int
1747Enable forcing TXG sync to find holes.
1748When enabled forces ZFS to sync data when
1749.Sy SEEK_HOLE No or Sy SEEK_DATA
1750flags are used allowing holes in a file to be accurately reported.
1751When disabled holes will not be reported in recently dirtied files.
1752.
1753.It Sy zfs_pd_bytes_max Ns = Ns Sy 52428800 Ns B Po 50 MiB Pc Pq int
1754The number of bytes which should be prefetched during a pool traversal, like
1755.Nm zfs Cm send
1756or other data crawling operations.
1757.
1758.It Sy zfs_traverse_indirect_prefetch_limit Ns = Ns Sy 32 Pq uint
1759The number of blocks pointed by indirect (non-L0) block which should be
1760prefetched during a pool traversal, like
1761.Nm zfs Cm send
1762or other data crawling operations.
1763.
1764.It Sy zfs_per_txg_dirty_frees_percent Ns = Ns Sy 30 Ns % Pq u64
1765Control percentage of dirtied indirect blocks from frees allowed into one TXG.
1766After this threshold is crossed, additional frees will wait until the next TXG.
1767.Sy 0 No disables this throttle .
1768.
1769.It Sy zfs_prefetch_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
1770Disable predictive prefetch.
1771Note that it leaves "prescient" prefetch
1772.Pq for, e.g., Nm zfs Cm send
1773intact.
1774Unlike predictive prefetch, prescient prefetch never issues I/O
1775that ends up not being needed, so it can't hurt performance.
1776.
1777.It Sy zfs_qat_checksum_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
1778Disable QAT hardware acceleration for SHA256 checksums.
1779May be unset after the ZFS modules have been loaded to initialize the QAT
1780hardware as long as support is compiled in and the QAT driver is present.
1781.
1782.It Sy zfs_qat_compress_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
1783Disable QAT hardware acceleration for gzip compression.
1784May be unset after the ZFS modules have been loaded to initialize the QAT
1785hardware as long as support is compiled in and the QAT driver is present.
1786.
1787.It Sy zfs_qat_encrypt_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
1788Disable QAT hardware acceleration for AES-GCM encryption.
1789May be unset after the ZFS modules have been loaded to initialize the QAT
1790hardware as long as support is compiled in and the QAT driver is present.
1791.
1792.It Sy zfs_vnops_read_chunk_size Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq u64
1793Bytes to read per chunk.
1794.
1795.It Sy zfs_read_history Ns = Ns Sy 0 Pq uint
1796Historical statistics for this many latest reads will be available in
1797.Pa /proc/spl/kstat/zfs/ Ns Ao Ar pool Ac Ns Pa /reads .
1798.
1799.It Sy zfs_read_history_hits Ns = Ns Sy 0 Ns | Ns 1 Pq int
1800Include cache hits in read history
1801.
1802.It Sy zfs_rebuild_max_segment Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq u64
1803Maximum read segment size to issue when sequentially resilvering a
1804top-level vdev.
1805.
1806.It Sy zfs_rebuild_scrub_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
1807Automatically start a pool scrub when the last active sequential resilver
1808completes in order to verify the checksums of all blocks which have been
1809resilvered.
1810This is enabled by default and strongly recommended.
1811.
1812.It Sy zfs_rebuild_vdev_limit Ns = Ns Sy 67108864 Ns B Po 64 MiB Pc Pq u64
1813Maximum amount of I/O that can be concurrently issued for a sequential
1814resilver per leaf device, given in bytes.
1815.
1816.It Sy zfs_reconstruct_indirect_combinations_max Ns = Ns Sy 4096 Pq int
1817If an indirect split block contains more than this many possible unique
1818combinations when being reconstructed, consider it too computationally
1819expensive to check them all.
1820Instead, try at most this many randomly selected
1821combinations each time the block is accessed.
1822This allows all segment copies to participate fairly
1823in the reconstruction when all combinations
1824cannot be checked and prevents repeated use of one bad copy.
1825.
1826.It Sy zfs_recover Ns = Ns Sy 0 Ns | Ns 1 Pq int
1827Set to attempt to recover from fatal errors.
1828This should only be used as a last resort,
1829as it typically results in leaked space, or worse.
1830.
1831.It Sy zfs_removal_ignore_errors Ns = Ns Sy 0 Ns | Ns 1 Pq int
1832Ignore hard I/O errors during device removal.
1833When set, if a device encounters a hard I/O error during the removal process
1834the removal will not be cancelled.
1835This can result in a normally recoverable block becoming permanently damaged
1836and is hence not recommended.
1837This should only be used as a last resort when the
1838pool cannot be returned to a healthy state prior to removing the device.
1839.
1840.It Sy zfs_removal_suspend_progress Ns = Ns Sy 0 Ns | Ns 1 Pq uint
1841This is used by the test suite so that it can ensure that certain actions
1842happen while in the middle of a removal.
1843.
1844.It Sy zfs_remove_max_segment Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq uint
1845The largest contiguous segment that we will attempt to allocate when removing
1846a device.
1847If there is a performance problem with attempting to allocate large blocks,
1848consider decreasing this.
1849The default value is also the maximum.
1850.
1851.It Sy zfs_resilver_disable_defer Ns = Ns Sy 0 Ns | Ns 1 Pq int
1852Ignore the
1853.Sy resilver_defer
1854feature, causing an operation that would start a resilver to
1855immediately restart the one in progress.
1856.
1857.It Sy zfs_resilver_min_time_ms Ns = Ns Sy 3000 Ns ms Po 3 s Pc Pq uint
1858Resilvers are processed by the sync thread.
1859While resilvering, it will spend at least this much time
1860working on a resilver between TXG flushes.
1861.
1862.It Sy zfs_scan_ignore_errors Ns = Ns Sy 0 Ns | Ns 1 Pq int
1863If set, remove the DTL (dirty time list) upon completion of a pool scan (scrub),
1864even if there were unrepairable errors.
1865Intended to be used during pool repair or recovery to
1866stop resilvering when the pool is next imported.
1867.
1868.It Sy zfs_scrub_after_expand Ns = Ns Sy 1 Ns | Ns 0 Pq int
1869Automatically start a pool scrub after a RAIDZ expansion completes
1870in order to verify the checksums of all blocks which have been
1871copied during the expansion.
1872This is enabled by default and strongly recommended.
1873.
1874.It Sy zfs_scrub_min_time_ms Ns = Ns Sy 1000 Ns ms Po 1 s Pc Pq uint
1875Scrubs are processed by the sync thread.
1876While scrubbing, it will spend at least this much time
1877working on a scrub between TXG flushes.
1878.
1879.It Sy zfs_scrub_error_blocks_per_txg Ns = Ns Sy 4096 Pq uint
1880Error blocks to be scrubbed in one txg.
1881.
1882.It Sy zfs_scan_checkpoint_intval Ns = Ns Sy 7200 Ns s Po 2 hour Pc Pq uint
1883To preserve progress across reboots, the sequential scan algorithm periodically
1884needs to stop metadata scanning and issue all the verification I/O to disk.
1885The frequency of this flushing is determined by this tunable.
1886.
1887.It Sy zfs_scan_fill_weight Ns = Ns Sy 3 Pq uint
1888This tunable affects how scrub and resilver I/O segments are ordered.
1889A higher number indicates that we care more about how filled in a segment is,
1890while a lower number indicates we care more about the size of the extent without
1891considering the gaps within a segment.
1892This value is only tunable upon module insertion.
1893Changing the value afterwards will have no effect on scrub or resilver
1894performance.
1895.
1896.It Sy zfs_scan_issue_strategy Ns = Ns Sy 0 Pq uint
1897Determines the order that data will be verified while scrubbing or resilvering:
1898.Bl -tag -compact -offset 4n -width "a"
1899.It Sy 1
1900Data will be verified as sequentially as possible, given the
1901amount of memory reserved for scrubbing
1902.Pq see Sy zfs_scan_mem_lim_fact .
1903This may improve scrub performance if the pool's data is very fragmented.
1904.It Sy 2
1905The largest mostly-contiguous chunk of found data will be verified first.
1906By deferring scrubbing of small segments, we may later find adjacent data
1907to coalesce and increase the segment size.
1908.It Sy 0
1909.No Use strategy Sy 1 No during normal verification
1910.No and strategy Sy 2 No while taking a checkpoint .
1911.El
1912.
1913.It Sy zfs_scan_legacy Ns = Ns Sy 0 Ns | Ns 1 Pq int
1914If unset, indicates that scrubs and resilvers will gather metadata in
1915memory before issuing sequential I/O.
1916Otherwise indicates that the legacy algorithm will be used,
1917where I/O is initiated as soon as it is discovered.
1918Unsetting will not affect scrubs or resilvers that are already in progress.
1919.
1920.It Sy zfs_scan_max_ext_gap Ns = Ns Sy 2097152 Ns B Po 2 MiB Pc Pq int
1921Sets the largest gap in bytes between scrub/resilver I/O operations
1922that will still be considered sequential for sorting purposes.
1923Changing this value will not
1924affect scrubs or resilvers that are already in progress.
1925.
1926.It Sy zfs_scan_mem_lim_fact Ns = Ns Sy 20 Ns ^-1 Pq uint
1927Maximum fraction of RAM used for I/O sorting by sequential scan algorithm.
1928This tunable determines the hard limit for I/O sorting memory usage.
1929When the hard limit is reached we stop scanning metadata and start issuing
1930data verification I/O.
1931This is done until we get below the soft limit.
1932.
1933.It Sy zfs_scan_mem_lim_soft_fact Ns = Ns Sy 20 Ns ^-1 Pq uint
1934The fraction of the hard limit used to determined the soft limit for I/O sorting
1935by the sequential scan algorithm.
1936When we cross this limit from below no action is taken.
1937When we cross this limit from above it is because we are issuing verification
1938I/O.
1939In this case (unless the metadata scan is done) we stop issuing verification I/O
1940and start scanning metadata again until we get to the hard limit.
1941.
1942.It Sy zfs_scan_report_txgs Ns = Ns Sy 0 Ns | Ns 1 Pq uint
1943When reporting resilver throughput and estimated completion time use the
1944performance observed over roughly the last
1945.Sy zfs_scan_report_txgs
1946TXGs.
1947When set to zero performance is calculated over the time between checkpoints.
1948.
1949.It Sy zfs_scan_strict_mem_lim Ns = Ns Sy 0 Ns | Ns 1 Pq int
1950Enforce tight memory limits on pool scans when a sequential scan is in progress.
1951When disabled, the memory limit may be exceeded by fast disks.
1952.
1953.It Sy zfs_scan_suspend_progress Ns = Ns Sy 0 Ns | Ns 1 Pq int
1954Freezes a scrub/resilver in progress without actually pausing it.
1955Intended for testing/debugging.
1956.
1957.It Sy zfs_scan_vdev_limit Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq int
1958Maximum amount of data that can be concurrently issued at once for scrubs and
1959resilvers per leaf device, given in bytes.
1960.
1961.It Sy zfs_send_corrupt_data Ns = Ns Sy 0 Ns | Ns 1 Pq int
1962Allow sending of corrupt data (ignore read/checksum errors when sending).
1963.
1964.It Sy zfs_send_unmodified_spill_blocks Ns = Ns Sy 1 Ns | Ns 0 Pq int
1965Include unmodified spill blocks in the send stream.
1966Under certain circumstances, previous versions of ZFS could incorrectly
1967remove the spill block from an existing object.
1968Including unmodified copies of the spill blocks creates a backwards-compatible
1969stream which will recreate a spill block if it was incorrectly removed.
1970.
1971.It Sy zfs_send_no_prefetch_queue_ff Ns = Ns Sy 20 Ns ^\-1 Pq uint
1972The fill fraction of the
1973.Nm zfs Cm send
1974internal queues.
1975The fill fraction controls the timing with which internal threads are woken up.
1976.
1977.It Sy zfs_send_no_prefetch_queue_length Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq uint
1978The maximum number of bytes allowed in
1979.Nm zfs Cm send Ns 's
1980internal queues.
1981.
1982.It Sy zfs_send_queue_ff Ns = Ns Sy 20 Ns ^\-1 Pq uint
1983The fill fraction of the
1984.Nm zfs Cm send
1985prefetch queue.
1986The fill fraction controls the timing with which internal threads are woken up.
1987.
1988.It Sy zfs_send_queue_length Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq uint
1989The maximum number of bytes allowed that will be prefetched by
1990.Nm zfs Cm send .
1991This value must be at least twice the maximum block size in use.
1992.
1993.It Sy zfs_recv_queue_ff Ns = Ns Sy 20 Ns ^\-1 Pq uint
1994The fill fraction of the
1995.Nm zfs Cm receive
1996queue.
1997The fill fraction controls the timing with which internal threads are woken up.
1998.
1999.It Sy zfs_recv_queue_length Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq uint
2000The maximum number of bytes allowed in the
2001.Nm zfs Cm receive
2002queue.
2003This value must be at least twice the maximum block size in use.
2004.
2005.It Sy zfs_recv_write_batch_size Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq uint
2006The maximum amount of data, in bytes, that
2007.Nm zfs Cm receive
2008will write in one DMU transaction.
2009This is the uncompressed size, even when receiving a compressed send stream.
2010This setting will not reduce the write size below a single block.
2011Capped at a maximum of
2012.Sy 32 MiB .
2013.
2014.It Sy zfs_recv_best_effort_corrective Ns = Ns Sy 0 Pq int
2015When this variable is set to non-zero a corrective receive:
2016.Bl -enum -compact -offset 4n -width "1."
2017.It
2018Does not enforce the restriction of source & destination snapshot GUIDs
2019matching.
2020.It
2021If there is an error during healing, the healing receive is not
2022terminated instead it moves on to the next record.
2023.El
2024.
2025.It Sy zfs_override_estimate_recordsize Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2026Setting this variable overrides the default logic for estimating block
2027sizes when doing a
2028.Nm zfs Cm send .
2029The default heuristic is that the average block size
2030will be the current recordsize.
2031Override this value if most data in your dataset is not of that size
2032and you require accurate zfs send size estimates.
2033.
2034.It Sy zfs_sync_pass_deferred_free Ns = Ns Sy 2 Pq uint
2035Flushing of data to disk is done in passes.
2036Defer frees starting in this pass.
2037.
2038.It Sy zfs_spa_discard_memory_limit Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq int
2039Maximum memory used for prefetching a checkpoint's space map on each
2040vdev while discarding the checkpoint.
2041.
2042.It Sy zfs_special_class_metadata_reserve_pct Ns = Ns Sy 25 Ns % Pq uint
2043Only allow small data blocks to be allocated on the special and dedup vdev
2044types when the available free space percentage on these vdevs exceeds this
2045value.
2046This ensures reserved space is available for pool metadata as the
2047special vdevs approach capacity.
2048.
2049.It Sy zfs_sync_pass_dont_compress Ns = Ns Sy 8 Pq uint
2050Starting in this sync pass, disable compression (including of metadata).
2051With the default setting, in practice, we don't have this many sync passes,
2052so this has no effect.
2053.Pp
2054The original intent was that disabling compression would help the sync passes
2055to converge.
2056However, in practice, disabling compression increases
2057the average number of sync passes; because when we turn compression off,
2058many blocks' size will change, and thus we have to re-allocate
2059(not overwrite) them.
2060It also increases the number of
2061.Em 128 KiB
2062allocations (e.g. for indirect blocks and spacemaps)
2063because these will not be compressed.
2064The
2065.Em 128 KiB
2066allocations are especially detrimental to performance
2067on highly fragmented systems, which may have very few free segments of this
2068size,
2069and may need to load new metaslabs to satisfy these allocations.
2070.
2071.It Sy zfs_sync_pass_rewrite Ns = Ns Sy 2 Pq uint
2072Rewrite new block pointers starting in this pass.
2073.
2074.It Sy zfs_trim_extent_bytes_max Ns = Ns Sy 134217728 Ns B Po 128 MiB Pc Pq uint
2075Maximum size of TRIM command.
2076Larger ranges will be split into chunks no larger than this value before
2077issuing.
2078.
2079.It Sy zfs_trim_extent_bytes_min Ns = Ns Sy 32768 Ns B Po 32 KiB Pc Pq uint
2080Minimum size of TRIM commands.
2081TRIM ranges smaller than this will be skipped,
2082unless they're part of a larger range which was chunked.
2083This is done because it's common for these small TRIMs
2084to negatively impact overall performance.
2085.
2086.It Sy zfs_trim_metaslab_skip Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2087Skip uninitialized metaslabs during the TRIM process.
2088This option is useful for pools constructed from large thinly-provisioned
2089devices
2090where TRIM operations are slow.
2091As a pool ages, an increasing fraction of the pool's metaslabs
2092will be initialized, progressively degrading the usefulness of this option.
2093This setting is stored when starting a manual TRIM and will
2094persist for the duration of the requested TRIM.
2095.
2096.It Sy zfs_trim_queue_limit Ns = Ns Sy 10 Pq uint
2097Maximum number of queued TRIMs outstanding per leaf vdev.
2098The number of concurrent TRIM commands issued to the device is controlled by
2099.Sy zfs_vdev_trim_min_active No and Sy zfs_vdev_trim_max_active .
2100.
2101.It Sy zfs_trim_txg_batch Ns = Ns Sy 32 Pq uint
2102The number of transaction groups' worth of frees which should be aggregated
2103before TRIM operations are issued to the device.
2104This setting represents a trade-off between issuing larger,
2105more efficient TRIM operations and the delay
2106before the recently trimmed space is available for use by the device.
2107.Pp
2108Increasing this value will allow frees to be aggregated for a longer time.
2109This will result is larger TRIM operations and potentially increased memory
2110usage.
2111Decreasing this value will have the opposite effect.
2112The default of
2113.Sy 32
2114was determined to be a reasonable compromise.
2115.
2116.It Sy zfs_txg_history Ns = Ns Sy 100 Pq uint
2117Historical statistics for this many latest TXGs will be available in
2118.Pa /proc/spl/kstat/zfs/ Ns Ao Ar pool Ac Ns Pa /TXGs .
2119.
2120.It Sy zfs_txg_timeout Ns = Ns Sy 5 Ns s Pq uint
2121Flush dirty data to disk at least every this many seconds (maximum TXG
2122duration).
2123.
2124.It Sy zfs_vdev_aggregation_limit Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq uint
2125Max vdev I/O aggregation size.
2126.
2127.It Sy zfs_vdev_aggregation_limit_non_rotating Ns = Ns Sy 131072 Ns B Po 128 KiB Pc Pq uint
2128Max vdev I/O aggregation size for non-rotating media.
2129.
2130.It Sy zfs_vdev_mirror_rotating_inc Ns = Ns Sy 0 Pq int
2131A number by which the balancing algorithm increments the load calculation for
2132the purpose of selecting the least busy mirror member when an I/O operation
2133immediately follows its predecessor on rotational vdevs
2134for the purpose of making decisions based on load.
2135.
2136.It Sy zfs_vdev_mirror_rotating_seek_inc Ns = Ns Sy 5 Pq int
2137A number by which the balancing algorithm increments the load calculation for
2138the purpose of selecting the least busy mirror member when an I/O operation
2139lacks locality as defined by
2140.Sy zfs_vdev_mirror_rotating_seek_offset .
2141Operations within this that are not immediately following the previous operation
2142are incremented by half.
2143.
2144.It Sy zfs_vdev_mirror_rotating_seek_offset Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq int
2145The maximum distance for the last queued I/O operation in which
2146the balancing algorithm considers an operation to have locality.
2147.No See Sx ZFS I/O SCHEDULER .
2148.
2149.It Sy zfs_vdev_mirror_non_rotating_inc Ns = Ns Sy 0 Pq int
2150A number by which the balancing algorithm increments the load calculation for
2151the purpose of selecting the least busy mirror member on non-rotational vdevs
2152when I/O operations do not immediately follow one another.
2153.
2154.It Sy zfs_vdev_mirror_non_rotating_seek_inc Ns = Ns Sy 1 Pq int
2155A number by which the balancing algorithm increments the load calculation for
2156the purpose of selecting the least busy mirror member when an I/O operation
2157lacks
2158locality as defined by the
2159.Sy zfs_vdev_mirror_rotating_seek_offset .
2160Operations within this that are not immediately following the previous operation
2161are incremented by half.
2162.
2163.It Sy zfs_vdev_read_gap_limit Ns = Ns Sy 32768 Ns B Po 32 KiB Pc Pq uint
2164Aggregate read I/O operations if the on-disk gap between them is within this
2165threshold.
2166.
2167.It Sy zfs_vdev_write_gap_limit Ns = Ns Sy 4096 Ns B Po 4 KiB Pc Pq uint
2168Aggregate write I/O operations if the on-disk gap between them is within this
2169threshold.
2170.
2171.It Sy zfs_vdev_raidz_impl Ns = Ns Sy fastest Pq string
2172Select the raidz parity implementation to use.
2173.Pp
2174Variants that don't depend on CPU-specific features
2175may be selected on module load, as they are supported on all systems.
2176The remaining options may only be set after the module is loaded,
2177as they are available only if the implementations are compiled in
2178and supported on the running system.
2179.Pp
2180Once the module is loaded,
2181.Pa /sys/module/zfs/parameters/zfs_vdev_raidz_impl
2182will show the available options,
2183with the currently selected one enclosed in square brackets.
2184.Pp
2185.TS
2186lb l l .
2187fastest	selected by built-in benchmark
2188original	original implementation
2189scalar	scalar implementation
2190sse2	SSE2 instruction set	64-bit x86
2191ssse3	SSSE3 instruction set	64-bit x86
2192avx2	AVX2 instruction set	64-bit x86
2193avx512f	AVX512F instruction set	64-bit x86
2194avx512bw	AVX512F & AVX512BW instruction sets	64-bit x86
2195aarch64_neon	NEON	Aarch64/64-bit ARMv8
2196aarch64_neonx2	NEON with more unrolling	Aarch64/64-bit ARMv8
2197powerpc_altivec	Altivec	PowerPC
2198.TE
2199.
2200.It Sy zfs_vdev_scheduler Pq charp
2201.Sy DEPRECATED .
2202Prints warning to kernel log for compatibility.
2203.
2204.It Sy zfs_zevent_len_max Ns = Ns Sy 512 Pq uint
2205Max event queue length.
2206Events in the queue can be viewed with
2207.Xr zpool-events 8 .
2208.
2209.It Sy zfs_zevent_retain_max Ns = Ns Sy 2000 Pq int
2210Maximum recent zevent records to retain for duplicate checking.
2211Setting this to
2212.Sy 0
2213disables duplicate detection.
2214.
2215.It Sy zfs_zevent_retain_expire_secs Ns = Ns Sy 900 Ns s Po 15 min Pc Pq int
2216Lifespan for a recent ereport that was retained for duplicate checking.
2217.
2218.It Sy zfs_zil_clean_taskq_maxalloc Ns = Ns Sy 1048576 Pq int
2219The maximum number of taskq entries that are allowed to be cached.
2220When this limit is exceeded transaction records (itxs)
2221will be cleaned synchronously.
2222.
2223.It Sy zfs_zil_clean_taskq_minalloc Ns = Ns Sy 1024 Pq int
2224The number of taskq entries that are pre-populated when the taskq is first
2225created and are immediately available for use.
2226.
2227.It Sy zfs_zil_clean_taskq_nthr_pct Ns = Ns Sy 100 Ns % Pq int
2228This controls the number of threads used by
2229.Sy dp_zil_clean_taskq .
2230The default value of
2231.Sy 100%
2232will create a maximum of one thread per cpu.
2233.
2234.It Sy zil_maxblocksize Ns = Ns Sy 131072 Ns B Po 128 KiB Pc Pq uint
2235This sets the maximum block size used by the ZIL.
2236On very fragmented pools, lowering this
2237.Pq typically to Sy 36 KiB
2238can improve performance.
2239.
2240.It Sy zil_maxcopied Ns = Ns Sy 7680 Ns B Po 7.5 KiB Pc Pq uint
2241This sets the maximum number of write bytes logged via WR_COPIED.
2242It tunes a tradeoff between additional memory copy and possibly worse log
2243space efficiency vs additional range lock/unlock.
2244.
2245.It Sy zil_nocacheflush Ns = Ns Sy 0 Ns | Ns 1 Pq int
2246Disable the cache flush commands that are normally sent to disk by
2247the ZIL after an LWB write has completed.
2248Setting this will cause ZIL corruption on power loss
2249if a volatile out-of-order write cache is enabled.
2250.
2251.It Sy zil_replay_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
2252Disable intent logging replay.
2253Can be disabled for recovery from corrupted ZIL.
2254.
2255.It Sy zil_slog_bulk Ns = Ns Sy 67108864 Ns B Po 64 MiB Pc Pq u64
2256Limit SLOG write size per commit executed with synchronous priority.
2257Any writes above that will be executed with lower (asynchronous) priority
2258to limit potential SLOG device abuse by single active ZIL writer.
2259.
2260.It Sy zfs_zil_saxattr Ns = Ns Sy 1 Ns | Ns 0 Pq int
2261Setting this tunable to zero disables ZIL logging of new
2262.Sy xattr Ns = Ns Sy sa
2263records if the
2264.Sy org.openzfs:zilsaxattr
2265feature is enabled on the pool.
2266This would only be necessary to work around bugs in the ZIL logging or replay
2267code for this record type.
2268The tunable has no effect if the feature is disabled.
2269.
2270.It Sy zfs_embedded_slog_min_ms Ns = Ns Sy 64 Pq uint
2271Usually, one metaslab from each normal-class vdev is dedicated for use by
2272the ZIL to log synchronous writes.
2273However, if there are fewer than
2274.Sy zfs_embedded_slog_min_ms
2275metaslabs in the vdev, this functionality is disabled.
2276This ensures that we don't set aside an unreasonable amount of space for the
2277ZIL.
2278.
2279.It Sy zstd_earlyabort_pass Ns = Ns Sy 1 Pq uint
2280Whether heuristic for detection of incompressible data with zstd levels >= 3
2281using LZ4 and zstd-1 passes is enabled.
2282.
2283.It Sy zstd_abort_size Ns = Ns Sy 131072 Pq uint
2284Minimal uncompressed size (inclusive) of a record before the early abort
2285heuristic will be attempted.
2286.
2287.It Sy zio_deadman_log_all Ns = Ns Sy 0 Ns | Ns 1 Pq int
2288If non-zero, the zio deadman will produce debugging messages
2289.Pq see Sy zfs_dbgmsg_enable
2290for all zios, rather than only for leaf zios possessing a vdev.
2291This is meant to be used by developers to gain
2292diagnostic information for hang conditions which don't involve a mutex
2293or other locking primitive: typically conditions in which a thread in
2294the zio pipeline is looping indefinitely.
2295.
2296.It Sy zio_slow_io_ms Ns = Ns Sy 30000 Ns ms Po 30 s Pc Pq int
2297When an I/O operation takes more than this much time to complete,
2298it's marked as slow.
2299Each slow operation causes a delay zevent.
2300Slow I/O counters can be seen with
2301.Nm zpool Cm status Fl s .
2302.
2303.It Sy zio_dva_throttle_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
2304Throttle block allocations in the I/O pipeline.
2305This allows for dynamic allocation distribution when devices are imbalanced.
2306When enabled, the maximum number of pending allocations per top-level vdev
2307is limited by
2308.Sy zfs_vdev_queue_depth_pct .
2309.
2310.It Sy zfs_xattr_compat Ns = Ns 0 Ns | Ns 1 Pq int
2311Control the naming scheme used when setting new xattrs in the user namespace.
2312If
2313.Sy 0
2314.Pq the default on Linux ,
2315user namespace xattr names are prefixed with the namespace, to be backwards
2316compatible with previous versions of ZFS on Linux.
2317If
2318.Sy 1
2319.Pq the default on Fx ,
2320user namespace xattr names are not prefixed, to be backwards compatible with
2321previous versions of ZFS on illumos and
2322.Fx .
2323.Pp
2324Either naming scheme can be read on this and future versions of ZFS, regardless
2325of this tunable, but legacy ZFS on illumos or
2326.Fx
2327are unable to read user namespace xattrs written in the Linux format, and
2328legacy versions of ZFS on Linux are unable to read user namespace xattrs written
2329in the legacy ZFS format.
2330.Pp
2331An existing xattr with the alternate naming scheme is removed when overwriting
2332the xattr so as to not accumulate duplicates.
2333.
2334.It Sy zio_requeue_io_start_cut_in_line Ns = Ns Sy 0 Ns | Ns 1 Pq int
2335Prioritize requeued I/O.
2336.
2337.It Sy zio_taskq_batch_pct Ns = Ns Sy 80 Ns % Pq uint
2338Percentage of online CPUs which will run a worker thread for I/O.
2339These workers are responsible for I/O work such as compression, encryption,
2340checksum and parity calculations.
2341Fractional number of CPUs will be rounded down.
2342.Pp
2343The default value of
2344.Sy 80%
2345was chosen to avoid using all CPUs which can result in
2346latency issues and inconsistent application performance,
2347especially when slower compression and/or checksumming is enabled.
2348Set value only applies to pools imported/created after that.
2349.
2350.It Sy zio_taskq_batch_tpq Ns = Ns Sy 0 Pq uint
2351Number of worker threads per taskq.
2352Higher values improve I/O ordering and CPU utilization,
2353while lower reduce lock contention.
2354Set value only applies to pools imported/created after that.
2355.Pp
2356If
2357.Sy 0 ,
2358generate a system-dependent value close to 6 threads per taskq.
2359Set value only applies to pools imported/created after that.
2360.
2361.It Sy zio_taskq_write_tpq Ns = Ns Sy 16 Pq uint
2362Determines the minumum number of threads per write issue taskq.
2363Higher values improve CPU utilization on high throughput,
2364while lower reduce taskq locks contention on high IOPS.
2365Set value only applies to pools imported/created after that.
2366.
2367.It Sy zio_taskq_read Ns = Ns Sy fixed,1,8 null scale null Pq charp
2368Set the queue and thread configuration for the IO read queues.
2369This is an advanced debugging parameter.
2370Don't change this unless you understand what it does.
2371Set values only apply to pools imported/created after that.
2372.
2373.It Sy zio_taskq_write Ns = Ns Sy sync null scale null Pq charp
2374Set the queue and thread configuration for the IO write queues.
2375This is an advanced debugging parameter.
2376Don't change this unless you understand what it does.
2377Set values only apply to pools imported/created after that.
2378.
2379.It Sy zvol_inhibit_dev Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2380Do not create zvol device nodes.
2381This may slightly improve startup time on
2382systems with a very large number of zvols.
2383.
2384.It Sy zvol_major Ns = Ns Sy 230 Pq uint
2385Major number for zvol block devices.
2386.
2387.It Sy zvol_max_discard_blocks Ns = Ns Sy 16384 Pq long
2388Discard (TRIM) operations done on zvols will be done in batches of this
2389many blocks, where block size is determined by the
2390.Sy volblocksize
2391property of a zvol.
2392.
2393.It Sy zvol_prefetch_bytes Ns = Ns Sy 131072 Ns B Po 128 KiB Pc Pq uint
2394When adding a zvol to the system, prefetch this many bytes
2395from the start and end of the volume.
2396Prefetching these regions of the volume is desirable,
2397because they are likely to be accessed immediately by
2398.Xr blkid 8
2399or the kernel partitioner.
2400.
2401.It Sy zvol_request_sync Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2402When processing I/O requests for a zvol, submit them synchronously.
2403This effectively limits the queue depth to
2404.Em 1
2405for each I/O submitter.
2406When unset, requests are handled asynchronously by a thread pool.
2407The number of requests which can be handled concurrently is controlled by
2408.Sy zvol_threads .
2409.Sy zvol_request_sync
2410is ignored when running on a kernel that supports block multiqueue
2411.Pq Li blk-mq .
2412.
2413.It Sy zvol_num_taskqs Ns = Ns Sy 0 Pq uint
2414Number of zvol taskqs.
2415If
2416.Sy 0
2417(the default) then scaling is done internally to prefer 6 threads per taskq.
2418This only applies on Linux.
2419.
2420.It Sy zvol_threads Ns = Ns Sy 0 Pq uint
2421The number of system wide threads to use for processing zvol block IOs.
2422If
2423.Sy 0
2424(the default) then internally set
2425.Sy zvol_threads
2426to the number of CPUs present or 32 (whichever is greater).
2427.
2428.It Sy zvol_blk_mq_threads Ns = Ns Sy 0 Pq uint
2429The number of threads per zvol to use for queuing IO requests.
2430This parameter will only appear if your kernel supports
2431.Li blk-mq
2432and is only read and assigned to a zvol at zvol load time.
2433If
2434.Sy 0
2435(the default) then internally set
2436.Sy zvol_blk_mq_threads
2437to the number of CPUs present.
2438.
2439.It Sy zvol_use_blk_mq Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2440Set to
2441.Sy 1
2442to use the
2443.Li blk-mq
2444API for zvols.
2445Set to
2446.Sy 0
2447(the default) to use the legacy zvol APIs.
2448This setting can give better or worse zvol performance depending on
2449the workload.
2450This parameter will only appear if your kernel supports
2451.Li blk-mq
2452and is only read and assigned to a zvol at zvol load time.
2453.
2454.It Sy zvol_blk_mq_blocks_per_thread Ns = Ns Sy 8 Pq uint
2455If
2456.Sy zvol_use_blk_mq
2457is enabled, then process this number of
2458.Sy volblocksize Ns -sized blocks per zvol thread.
2459This tunable can be use to favor better performance for zvol reads (lower
2460values) or writes (higher values).
2461If set to
2462.Sy 0 ,
2463then the zvol layer will process the maximum number of blocks
2464per thread that it can.
2465This parameter will only appear if your kernel supports
2466.Li blk-mq
2467and is only applied at each zvol's load time.
2468.
2469.It Sy zvol_blk_mq_queue_depth Ns = Ns Sy 0 Pq uint
2470The queue_depth value for the zvol
2471.Li blk-mq
2472interface.
2473This parameter will only appear if your kernel supports
2474.Li blk-mq
2475and is only applied at each zvol's load time.
2476If
2477.Sy 0
2478(the default) then use the kernel's default queue depth.
2479Values are clamped to the kernel's
2480.Dv BLKDEV_MIN_RQ
2481and
2482.Dv BLKDEV_MAX_RQ Ns / Ns Dv BLKDEV_DEFAULT_RQ
2483limits.
2484.
2485.It Sy zvol_volmode Ns = Ns Sy 1 Pq uint
2486Defines zvol block devices behaviour when
2487.Sy volmode Ns = Ns Sy default :
2488.Bl -tag -compact -offset 4n -width "a"
2489.It Sy 1
2490.No equivalent to Sy full
2491.It Sy 2
2492.No equivalent to Sy dev
2493.It Sy 3
2494.No equivalent to Sy none
2495.El
2496.
2497.It Sy zvol_enforce_quotas Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2498Enable strict ZVOL quota enforcement.
2499The strict quota enforcement may have a performance impact.
2500.El
2501.
2502.Sh ZFS I/O SCHEDULER
2503ZFS issues I/O operations to leaf vdevs to satisfy and complete I/O operations.
2504The scheduler determines when and in what order those operations are issued.
2505The scheduler divides operations into five I/O classes,
2506prioritized in the following order: sync read, sync write, async read,
2507async write, and scrub/resilver.
2508Each queue defines the minimum and maximum number of concurrent operations
2509that may be issued to the device.
2510In addition, the device has an aggregate maximum,
2511.Sy zfs_vdev_max_active .
2512Note that the sum of the per-queue minima must not exceed the aggregate maximum.
2513If the sum of the per-queue maxima exceeds the aggregate maximum,
2514then the number of active operations may reach
2515.Sy zfs_vdev_max_active ,
2516in which case no further operations will be issued,
2517regardless of whether all per-queue minima have been met.
2518.Pp
2519For many physical devices, throughput increases with the number of
2520concurrent operations, but latency typically suffers.
2521Furthermore, physical devices typically have a limit
2522at which more concurrent operations have no
2523effect on throughput or can actually cause it to decrease.
2524.Pp
2525The scheduler selects the next operation to issue by first looking for an
2526I/O class whose minimum has not been satisfied.
2527Once all are satisfied and the aggregate maximum has not been hit,
2528the scheduler looks for classes whose maximum has not been satisfied.
2529Iteration through the I/O classes is done in the order specified above.
2530No further operations are issued
2531if the aggregate maximum number of concurrent operations has been hit,
2532or if there are no operations queued for an I/O class that has not hit its
2533maximum.
2534Every time an I/O operation is queued or an operation completes,
2535the scheduler looks for new operations to issue.
2536.Pp
2537In general, smaller
2538.Sy max_active Ns s
2539will lead to lower latency of synchronous operations.
2540Larger
2541.Sy max_active Ns s
2542may lead to higher overall throughput, depending on underlying storage.
2543.Pp
2544The ratio of the queues'
2545.Sy max_active Ns s
2546determines the balance of performance between reads, writes, and scrubs.
2547For example, increasing
2548.Sy zfs_vdev_scrub_max_active
2549will cause the scrub or resilver to complete more quickly,
2550but reads and writes to have higher latency and lower throughput.
2551.Pp
2552All I/O classes have a fixed maximum number of outstanding operations,
2553except for the async write class.
2554Asynchronous writes represent the data that is committed to stable storage
2555during the syncing stage for transaction groups.
2556Transaction groups enter the syncing state periodically,
2557so the number of queued async writes will quickly burst up
2558and then bleed down to zero.
2559Rather than servicing them as quickly as possible,
2560the I/O scheduler changes the maximum number of active async write operations
2561according to the amount of dirty data in the pool.
2562Since both throughput and latency typically increase with the number of
2563concurrent operations issued to physical devices, reducing the
2564burstiness in the number of simultaneous operations also stabilizes the
2565response time of operations from other queues, in particular synchronous ones.
2566In broad strokes, the I/O scheduler will issue more concurrent operations
2567from the async write queue as there is more dirty data in the pool.
2568.
2569.Ss Async Writes
2570The number of concurrent operations issued for the async write I/O class
2571follows a piece-wise linear function defined by a few adjustable points:
2572.Bd -literal
2573       |              o---------| <-- \fBzfs_vdev_async_write_max_active\fP
2574  ^    |             /^         |
2575  |    |            / |         |
2576active |           /  |         |
2577 I/O   |          /   |         |
2578count  |         /    |         |
2579       |        /     |         |
2580       |-------o      |         | <-- \fBzfs_vdev_async_write_min_active\fP
2581      0|_______^______|_________|
2582       0%      |      |       100% of \fBzfs_dirty_data_max\fP
2583               |      |
2584               |      `-- \fBzfs_vdev_async_write_active_max_dirty_percent\fP
2585               `--------- \fBzfs_vdev_async_write_active_min_dirty_percent\fP
2586.Ed
2587.Pp
2588Until the amount of dirty data exceeds a minimum percentage of the dirty
2589data allowed in the pool, the I/O scheduler will limit the number of
2590concurrent operations to the minimum.
2591As that threshold is crossed, the number of concurrent operations issued
2592increases linearly to the maximum at the specified maximum percentage
2593of the dirty data allowed in the pool.
2594.Pp
2595Ideally, the amount of dirty data on a busy pool will stay in the sloped
2596part of the function between
2597.Sy zfs_vdev_async_write_active_min_dirty_percent
2598and
2599.Sy zfs_vdev_async_write_active_max_dirty_percent .
2600If it exceeds the maximum percentage,
2601this indicates that the rate of incoming data is
2602greater than the rate that the backend storage can handle.
2603In this case, we must further throttle incoming writes,
2604as described in the next section.
2605.
2606.Sh ZFS TRANSACTION DELAY
2607We delay transactions when we've determined that the backend storage
2608isn't able to accommodate the rate of incoming writes.
2609.Pp
2610If there is already a transaction waiting, we delay relative to when
2611that transaction will finish waiting.
2612This way the calculated delay time
2613is independent of the number of threads concurrently executing transactions.
2614.Pp
2615If we are the only waiter, wait relative to when the transaction started,
2616rather than the current time.
2617This credits the transaction for "time already served",
2618e.g. reading indirect blocks.
2619.Pp
2620The minimum time for a transaction to take is calculated as
2621.D1 min_time = min( Ns Sy zfs_delay_scale No \(mu Po Sy dirty No \- Sy min Pc / Po Sy max No \- Sy dirty Pc , 100ms)
2622.Pp
2623The delay has two degrees of freedom that can be adjusted via tunables.
2624The percentage of dirty data at which we start to delay is defined by
2625.Sy zfs_delay_min_dirty_percent .
2626This should typically be at or above
2627.Sy zfs_vdev_async_write_active_max_dirty_percent ,
2628so that we only start to delay after writing at full speed
2629has failed to keep up with the incoming write rate.
2630The scale of the curve is defined by
2631.Sy zfs_delay_scale .
2632Roughly speaking, this variable determines the amount of delay at the midpoint
2633of the curve.
2634.Bd -literal
2635delay
2636 10ms +-------------------------------------------------------------*+
2637      |                                                             *|
2638  9ms +                                                             *+
2639      |                                                             *|
2640  8ms +                                                             *+
2641      |                                                            * |
2642  7ms +                                                            * +
2643      |                                                            * |
2644  6ms +                                                            * +
2645      |                                                            * |
2646  5ms +                                                           *  +
2647      |                                                           *  |
2648  4ms +                                                           *  +
2649      |                                                           *  |
2650  3ms +                                                          *   +
2651      |                                                          *   |
2652  2ms +                                              (midpoint) *    +
2653      |                                                  |    **     |
2654  1ms +                                                  v ***       +
2655      |             \fBzfs_delay_scale\fP ---------->     ********         |
2656    0 +-------------------------------------*********----------------+
2657      0%                    <- \fBzfs_dirty_data_max\fP ->               100%
2658.Ed
2659.Pp
2660Note, that since the delay is added to the outstanding time remaining on the
2661most recent transaction it's effectively the inverse of IOPS.
2662Here, the midpoint of
2663.Em 500 us
2664translates to
2665.Em 2000 IOPS .
2666The shape of the curve
2667was chosen such that small changes in the amount of accumulated dirty data
2668in the first three quarters of the curve yield relatively small differences
2669in the amount of delay.
2670.Pp
2671The effects can be easier to understand when the amount of delay is
2672represented on a logarithmic scale:
2673.Bd -literal
2674delay
2675100ms +-------------------------------------------------------------++
2676      +                                                              +
2677      |                                                              |
2678      +                                                             *+
2679 10ms +                                                             *+
2680      +                                                           ** +
2681      |                                              (midpoint)  **  |
2682      +                                                  |     **    +
2683  1ms +                                                  v ****      +
2684      +             \fBzfs_delay_scale\fP ---------->        *****         +
2685      |                                             ****             |
2686      +                                          ****                +
2687100us +                                        **                    +
2688      +                                       *                      +
2689      |                                      *                       |
2690      +                                     *                        +
2691 10us +                                     *                        +
2692      +                                                              +
2693      |                                                              |
2694      +                                                              +
2695      +--------------------------------------------------------------+
2696      0%                    <- \fBzfs_dirty_data_max\fP ->               100%
2697.Ed
2698.Pp
2699Note here that only as the amount of dirty data approaches its limit does
2700the delay start to increase rapidly.
2701The goal of a properly tuned system should be to keep the amount of dirty data
2702out of that range by first ensuring that the appropriate limits are set
2703for the I/O scheduler to reach optimal throughput on the back-end storage,
2704and then by changing the value of
2705.Sy zfs_delay_scale
2706to increase the steepness of the curve.
2707