xref: /freebsd/sys/contrib/openzfs/man/man4/zfs.4 (revision 894cb08f0d3656fdb81f4d89085bedc4235f3cb6)
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 February 14, 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_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
910When a pool sync operation takes longer than
911.Sy zfs_deadman_synctime_ms ,
912or when an individual I/O operation takes longer than
913.Sy zfs_deadman_ziotime_ms ,
914then the operation is considered to be "hung".
915If
916.Sy zfs_deadman_enabled
917is set, then the deadman behavior is invoked as described by
918.Sy zfs_deadman_failmode .
919By default, the deadman is enabled and set to
920.Sy wait
921which results in "hung" I/O operations only being logged.
922The deadman is automatically disabled when a pool gets suspended.
923.
924.It Sy zfs_deadman_failmode Ns = Ns Sy wait Pq charp
925Controls the failure behavior when the deadman detects a "hung" I/O operation.
926Valid values are:
927.Bl -tag -compact -offset 4n -width "continue"
928.It Sy wait
929Wait for a "hung" operation to complete.
930For each "hung" operation a "deadman" event will be posted
931describing that operation.
932.It Sy continue
933Attempt to recover from a "hung" operation by re-dispatching it
934to the I/O pipeline if possible.
935.It Sy panic
936Panic the system.
937This can be used to facilitate automatic fail-over
938to a properly configured fail-over partner.
939.El
940.
941.It Sy zfs_deadman_checktime_ms Ns = Ns Sy 60000 Ns ms Po 1 min Pc Pq u64
942Check time in milliseconds.
943This defines the frequency at which we check for hung I/O requests
944and potentially invoke the
945.Sy zfs_deadman_failmode
946behavior.
947.
948.It Sy zfs_deadman_synctime_ms Ns = Ns Sy 600000 Ns ms Po 10 min Pc Pq u64
949Interval in milliseconds after which the deadman is triggered and also
950the interval after which a pool sync operation is considered to be "hung".
951Once this limit is exceeded the deadman will be invoked every
952.Sy zfs_deadman_checktime_ms
953milliseconds until the pool sync completes.
954.
955.It Sy zfs_deadman_ziotime_ms Ns = Ns Sy 300000 Ns ms Po 5 min Pc Pq u64
956Interval in milliseconds after which the deadman is triggered and an
957individual I/O operation is considered to be "hung".
958As long as the operation remains "hung",
959the deadman will be invoked every
960.Sy zfs_deadman_checktime_ms
961milliseconds until the operation completes.
962.
963.It Sy zfs_dedup_prefetch Ns = Ns Sy 0 Ns | Ns 1 Pq int
964Enable prefetching dedup-ed blocks which are going to be freed.
965.
966.It Sy zfs_delay_min_dirty_percent Ns = Ns Sy 60 Ns % Pq uint
967Start to delay each transaction once there is this amount of dirty data,
968expressed as a percentage of
969.Sy zfs_dirty_data_max .
970This value should be at least
971.Sy zfs_vdev_async_write_active_max_dirty_percent .
972.No See Sx ZFS TRANSACTION DELAY .
973.
974.It Sy zfs_delay_scale Ns = Ns Sy 500000 Pq int
975This controls how quickly the transaction delay approaches infinity.
976Larger values cause longer delays for a given amount of dirty data.
977.Pp
978For the smoothest delay, this value should be about 1 billion divided
979by the maximum number of operations per second.
980This will smoothly handle between ten times and a tenth of this number.
981.No See Sx ZFS TRANSACTION DELAY .
982.Pp
983.Sy zfs_delay_scale No \(mu Sy zfs_dirty_data_max Em must No be smaller than Sy 2^64 .
984.
985.It Sy zfs_disable_ivset_guid_check Ns = Ns Sy 0 Ns | Ns 1 Pq int
986Disables requirement for IVset GUIDs to be present and match when doing a raw
987receive of encrypted datasets.
988Intended for users whose pools were created with
989OpenZFS pre-release versions and now have compatibility issues.
990.
991.It Sy zfs_key_max_salt_uses Ns = Ns Sy 400000000 Po 4*10^8 Pc Pq ulong
992Maximum number of uses of a single salt value before generating a new one for
993encrypted datasets.
994The default value is also the maximum.
995.
996.It Sy zfs_object_mutex_size Ns = Ns Sy 64 Pq uint
997Size of the znode hashtable used for holds.
998.Pp
999Due to the need to hold locks on objects that may not exist yet, kernel mutexes
1000are not created per-object and instead a hashtable is used where collisions
1001will result in objects waiting when there is not actually contention on the
1002same object.
1003.
1004.It Sy zfs_slow_io_events_per_second Ns = Ns Sy 20 Ns /s Pq int
1005Rate limit delay and deadman zevents (which report slow I/O operations) to this
1006many per
1007second.
1008.
1009.It Sy zfs_unflushed_max_mem_amt Ns = Ns Sy 1073741824 Ns B Po 1 GiB Pc Pq u64
1010Upper-bound limit for unflushed metadata changes to be held by the
1011log spacemap in memory, in bytes.
1012.
1013.It Sy zfs_unflushed_max_mem_ppm Ns = Ns Sy 1000 Ns ppm Po 0.1% Pc Pq u64
1014Part of overall system memory that ZFS allows to be used
1015for unflushed metadata changes by the log spacemap, in millionths.
1016.
1017.It Sy zfs_unflushed_log_block_max Ns = Ns Sy 131072 Po 128k Pc Pq u64
1018Describes the maximum number of log spacemap blocks allowed for each pool.
1019The default value means that the space in all the log spacemaps
1020can add up to no more than
1021.Sy 131072
1022blocks (which means
1023.Em 16 GiB
1024of logical space before compression and ditto blocks,
1025assuming that blocksize is
1026.Em 128 KiB ) .
1027.Pp
1028This tunable is important because it involves a trade-off between import
1029time after an unclean export and the frequency of flushing metaslabs.
1030The higher this number is, the more log blocks we allow when the pool is
1031active which means that we flush metaslabs less often and thus decrease
1032the number of I/O operations for spacemap updates per TXG.
1033At the same time though, that means that in the event of an unclean export,
1034there will be more log spacemap blocks for us to read, inducing overhead
1035in the import time of the pool.
1036The lower the number, the amount of flushing increases, destroying log
1037blocks quicker as they become obsolete faster, which leaves less blocks
1038to be read during import time after a crash.
1039.Pp
1040Each log spacemap block existing during pool import leads to approximately
1041one extra logical I/O issued.
1042This is the reason why this tunable is exposed in terms of blocks rather
1043than space used.
1044.
1045.It Sy zfs_unflushed_log_block_min Ns = Ns Sy 1000 Pq u64
1046If the number of metaslabs is small and our incoming rate is high,
1047we could get into a situation that we are flushing all our metaslabs every TXG.
1048Thus we always allow at least this many log blocks.
1049.
1050.It Sy zfs_unflushed_log_block_pct Ns = Ns Sy 400 Ns % Pq u64
1051Tunable used to determine the number of blocks that can be used for
1052the spacemap log, expressed as a percentage of the total number of
1053unflushed metaslabs in the pool.
1054.
1055.It Sy zfs_unflushed_log_txg_max Ns = Ns Sy 1000 Pq u64
1056Tunable limiting maximum time in TXGs any metaslab may remain unflushed.
1057It effectively limits maximum number of unflushed per-TXG spacemap logs
1058that need to be read after unclean pool export.
1059.
1060.It Sy zfs_unlink_suspend_progress Ns = Ns Sy 0 Ns | Ns 1 Pq uint
1061When enabled, files will not be asynchronously removed from the list of pending
1062unlinks and the space they consume will be leaked.
1063Once this option has been disabled and the dataset is remounted,
1064the pending unlinks will be processed and the freed space returned to the pool.
1065This option is used by the test suite.
1066.
1067.It Sy zfs_delete_blocks Ns = Ns Sy 20480 Pq ulong
1068This is the used to define a large file for the purposes of deletion.
1069Files containing more than
1070.Sy zfs_delete_blocks
1071will be deleted asynchronously, while smaller files are deleted synchronously.
1072Decreasing this value will reduce the time spent in an
1073.Xr unlink 2
1074system call, at the expense of a longer delay before the freed space is
1075available.
1076This only applies on Linux.
1077.
1078.It Sy zfs_dirty_data_max Ns = Pq int
1079Determines the dirty space limit in bytes.
1080Once this limit is exceeded, new writes are halted until space frees up.
1081This parameter takes precedence over
1082.Sy zfs_dirty_data_max_percent .
1083.No See Sx ZFS TRANSACTION DELAY .
1084.Pp
1085Defaults to
1086.Sy physical_ram/10 ,
1087capped at
1088.Sy zfs_dirty_data_max_max .
1089.
1090.It Sy zfs_dirty_data_max_max Ns = Pq int
1091Maximum allowable value of
1092.Sy zfs_dirty_data_max ,
1093expressed in bytes.
1094This limit is only enforced at module load time, and will be ignored if
1095.Sy zfs_dirty_data_max
1096is later changed.
1097This parameter takes precedence over
1098.Sy zfs_dirty_data_max_max_percent .
1099.No See Sx ZFS TRANSACTION DELAY .
1100.Pp
1101Defaults to
1102.Sy min(physical_ram/4, 4GiB) ,
1103or
1104.Sy min(physical_ram/4, 1GiB)
1105for 32-bit systems.
1106.
1107.It Sy zfs_dirty_data_max_max_percent Ns = Ns Sy 25 Ns % Pq uint
1108Maximum allowable value of
1109.Sy zfs_dirty_data_max ,
1110expressed as a percentage of physical RAM.
1111This limit is only enforced at module load time, and will be ignored if
1112.Sy zfs_dirty_data_max
1113is later changed.
1114The parameter
1115.Sy zfs_dirty_data_max_max
1116takes precedence over this one.
1117.No See Sx ZFS TRANSACTION DELAY .
1118.
1119.It Sy zfs_dirty_data_max_percent Ns = Ns Sy 10 Ns % Pq uint
1120Determines the dirty space limit, expressed as a percentage of all memory.
1121Once this limit is exceeded, new writes are halted until space frees up.
1122The parameter
1123.Sy zfs_dirty_data_max
1124takes precedence over this one.
1125.No See Sx ZFS TRANSACTION DELAY .
1126.Pp
1127Subject to
1128.Sy zfs_dirty_data_max_max .
1129.
1130.It Sy zfs_dirty_data_sync_percent Ns = Ns Sy 20 Ns % Pq uint
1131Start syncing out a transaction group if there's at least this much dirty data
1132.Pq as a percentage of Sy zfs_dirty_data_max .
1133This should be less than
1134.Sy zfs_vdev_async_write_active_min_dirty_percent .
1135.
1136.It Sy zfs_wrlog_data_max Ns = Pq int
1137The upper limit of write-transaction zil log data size in bytes.
1138Write operations are throttled when approaching the limit until log data is
1139cleared out after transaction group sync.
1140Because of some overhead, it should be set at least 2 times the size of
1141.Sy zfs_dirty_data_max
1142.No to prevent harming normal write throughput .
1143It also should be smaller than the size of the slog device if slog is present.
1144.Pp
1145Defaults to
1146.Sy zfs_dirty_data_max*2
1147.
1148.It Sy zfs_fallocate_reserve_percent Ns = Ns Sy 110 Ns % Pq uint
1149Since ZFS is a copy-on-write filesystem with snapshots, blocks cannot be
1150preallocated for a file in order to guarantee that later writes will not
1151run out of space.
1152Instead,
1153.Xr fallocate 2
1154space preallocation only checks that sufficient space is currently available
1155in the pool or the user's project quota allocation,
1156and then creates a sparse file of the requested size.
1157The requested space is multiplied by
1158.Sy zfs_fallocate_reserve_percent
1159to allow additional space for indirect blocks and other internal metadata.
1160Setting this to
1161.Sy 0
1162disables support for
1163.Xr fallocate 2
1164and causes it to return
1165.Sy EOPNOTSUPP .
1166.
1167.It Sy zfs_fletcher_4_impl Ns = Ns Sy fastest Pq string
1168Select a fletcher 4 implementation.
1169.Pp
1170Supported selectors are:
1171.Sy fastest , scalar , sse2 , ssse3 , avx2 , avx512f , avx512bw ,
1172.No and Sy aarch64_neon .
1173All except
1174.Sy fastest No and Sy scalar
1175require instruction set extensions to be available,
1176and will only appear if ZFS detects that they are present at runtime.
1177If multiple implementations of fletcher 4 are available, the
1178.Sy fastest
1179will be chosen using a micro benchmark.
1180Selecting
1181.Sy scalar
1182results in the original CPU-based calculation being used.
1183Selecting any option other than
1184.Sy fastest No or Sy scalar
1185results in vector instructions
1186from the respective CPU instruction set being used.
1187.
1188.It Sy zfs_bclone_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
1189Enable the experimental block cloning feature.
1190If this setting is 0, then even if feature@block_cloning is enabled,
1191attempts to clone blocks will act as though the feature is disabled.
1192.
1193.It Sy zfs_bclone_wait_dirty Ns = Ns Sy 0 Ns | Ns 1 Pq int
1194When set to 1 the FICLONE and FICLONERANGE ioctls wait for dirty data to be
1195written to disk.
1196This allows the clone operation to reliably succeed when a file is
1197modified and then immediately cloned.
1198For small files this may be slower than making a copy of the file.
1199Therefore, this setting defaults to 0 which causes a clone operation to
1200immediately fail when encountering a dirty block.
1201.
1202.It Sy zfs_blake3_impl Ns = Ns Sy fastest Pq string
1203Select a BLAKE3 implementation.
1204.Pp
1205Supported selectors are:
1206.Sy cycle , fastest , generic , sse2 , sse41 , avx2 , avx512 .
1207All except
1208.Sy cycle , fastest No and Sy generic
1209require instruction set extensions to be available,
1210and will only appear if ZFS detects that they are present at runtime.
1211If multiple implementations of BLAKE3 are available, the
1212.Sy fastest will be chosen using a micro benchmark. You can see the
1213benchmark results by reading this kstat file:
1214.Pa /proc/spl/kstat/zfs/chksum_bench .
1215.
1216.It Sy zfs_free_bpobj_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
1217Enable/disable the processing of the free_bpobj object.
1218.
1219.It Sy zfs_async_block_max_blocks Ns = Ns Sy UINT64_MAX Po unlimited Pc Pq u64
1220Maximum number of blocks freed in a single TXG.
1221.
1222.It Sy zfs_max_async_dedup_frees Ns = Ns Sy 100000 Po 10^5 Pc Pq u64
1223Maximum number of dedup blocks freed in a single TXG.
1224.
1225.It Sy zfs_vdev_async_read_max_active Ns = Ns Sy 3 Pq uint
1226Maximum asynchronous read I/O operations active to each device.
1227.No See Sx ZFS I/O SCHEDULER .
1228.
1229.It Sy zfs_vdev_async_read_min_active Ns = Ns Sy 1 Pq uint
1230Minimum asynchronous read I/O operation active to each device.
1231.No See Sx ZFS I/O SCHEDULER .
1232.
1233.It Sy zfs_vdev_async_write_active_max_dirty_percent Ns = Ns Sy 60 Ns % Pq uint
1234When the pool has more than this much dirty data, use
1235.Sy zfs_vdev_async_write_max_active
1236to limit active async writes.
1237If the dirty data is between the minimum and maximum,
1238the active I/O limit is linearly interpolated.
1239.No See Sx ZFS I/O SCHEDULER .
1240.
1241.It Sy zfs_vdev_async_write_active_min_dirty_percent Ns = Ns Sy 30 Ns % Pq uint
1242When the pool has less than this much dirty data, use
1243.Sy zfs_vdev_async_write_min_active
1244to limit active async writes.
1245If the dirty data is between the minimum and maximum,
1246the active I/O limit is linearly
1247interpolated.
1248.No See Sx ZFS I/O SCHEDULER .
1249.
1250.It Sy zfs_vdev_async_write_max_active Ns = Ns Sy 10 Pq uint
1251Maximum asynchronous write I/O operations active to each device.
1252.No See Sx ZFS I/O SCHEDULER .
1253.
1254.It Sy zfs_vdev_async_write_min_active Ns = Ns Sy 2 Pq uint
1255Minimum asynchronous write I/O operations active to each device.
1256.No See Sx ZFS I/O SCHEDULER .
1257.Pp
1258Lower values are associated with better latency on rotational media but poorer
1259resilver performance.
1260The default value of
1261.Sy 2
1262was chosen as a compromise.
1263A value of
1264.Sy 3
1265has been shown to improve resilver performance further at a cost of
1266further increasing latency.
1267.
1268.It Sy zfs_vdev_initializing_max_active Ns = Ns Sy 1 Pq uint
1269Maximum initializing I/O operations active to each device.
1270.No See Sx ZFS I/O SCHEDULER .
1271.
1272.It Sy zfs_vdev_initializing_min_active Ns = Ns Sy 1 Pq uint
1273Minimum initializing I/O operations active to each device.
1274.No See Sx ZFS I/O SCHEDULER .
1275.
1276.It Sy zfs_vdev_max_active Ns = Ns Sy 1000 Pq uint
1277The maximum number of I/O operations active to each device.
1278Ideally, this will be at least the sum of each queue's
1279.Sy max_active .
1280.No See Sx ZFS I/O SCHEDULER .
1281.
1282.It Sy zfs_vdev_open_timeout_ms Ns = Ns Sy 1000 Pq uint
1283Timeout value to wait before determining a device is missing
1284during import.
1285This is helpful for transient missing paths due
1286to links being briefly removed and recreated in response to
1287udev events.
1288.
1289.It Sy zfs_vdev_rebuild_max_active Ns = Ns Sy 3 Pq uint
1290Maximum sequential resilver I/O operations active to each device.
1291.No See Sx ZFS I/O SCHEDULER .
1292.
1293.It Sy zfs_vdev_rebuild_min_active Ns = Ns Sy 1 Pq uint
1294Minimum sequential resilver I/O operations active to each device.
1295.No See Sx ZFS I/O SCHEDULER .
1296.
1297.It Sy zfs_vdev_removal_max_active Ns = Ns Sy 2 Pq uint
1298Maximum removal I/O operations active to each device.
1299.No See Sx ZFS I/O SCHEDULER .
1300.
1301.It Sy zfs_vdev_removal_min_active Ns = Ns Sy 1 Pq uint
1302Minimum removal I/O operations active to each device.
1303.No See Sx ZFS I/O SCHEDULER .
1304.
1305.It Sy zfs_vdev_scrub_max_active Ns = Ns Sy 2 Pq uint
1306Maximum scrub I/O operations active to each device.
1307.No See Sx ZFS I/O SCHEDULER .
1308.
1309.It Sy zfs_vdev_scrub_min_active Ns = Ns Sy 1 Pq uint
1310Minimum scrub I/O operations active to each device.
1311.No See Sx ZFS I/O SCHEDULER .
1312.
1313.It Sy zfs_vdev_sync_read_max_active Ns = Ns Sy 10 Pq uint
1314Maximum synchronous read I/O operations active to each device.
1315.No See Sx ZFS I/O SCHEDULER .
1316.
1317.It Sy zfs_vdev_sync_read_min_active Ns = Ns Sy 10 Pq uint
1318Minimum synchronous read I/O operations active to each device.
1319.No See Sx ZFS I/O SCHEDULER .
1320.
1321.It Sy zfs_vdev_sync_write_max_active Ns = Ns Sy 10 Pq uint
1322Maximum synchronous write I/O operations active to each device.
1323.No See Sx ZFS I/O SCHEDULER .
1324.
1325.It Sy zfs_vdev_sync_write_min_active Ns = Ns Sy 10 Pq uint
1326Minimum synchronous write I/O operations active to each device.
1327.No See Sx ZFS I/O SCHEDULER .
1328.
1329.It Sy zfs_vdev_trim_max_active Ns = Ns Sy 2 Pq uint
1330Maximum trim/discard I/O operations active to each device.
1331.No See Sx ZFS I/O SCHEDULER .
1332.
1333.It Sy zfs_vdev_trim_min_active Ns = Ns Sy 1 Pq uint
1334Minimum trim/discard I/O operations active to each device.
1335.No See Sx ZFS I/O SCHEDULER .
1336.
1337.It Sy zfs_vdev_nia_delay Ns = Ns Sy 5 Pq uint
1338For non-interactive I/O (scrub, resilver, removal, initialize and rebuild),
1339the number of concurrently-active I/O operations is limited to
1340.Sy zfs_*_min_active ,
1341unless the vdev is "idle".
1342When there are no interactive I/O operations active (synchronous or otherwise),
1343and
1344.Sy zfs_vdev_nia_delay
1345operations have completed since the last interactive operation,
1346then the vdev is considered to be "idle",
1347and the number of concurrently-active non-interactive operations is increased to
1348.Sy zfs_*_max_active .
1349.No See Sx ZFS I/O SCHEDULER .
1350.
1351.It Sy zfs_vdev_nia_credit Ns = Ns Sy 5 Pq uint
1352Some HDDs tend to prioritize sequential I/O so strongly, that concurrent
1353random I/O latency reaches several seconds.
1354On some HDDs this happens even if sequential I/O operations
1355are submitted one at a time, and so setting
1356.Sy zfs_*_max_active Ns = Sy 1
1357does not help.
1358To prevent non-interactive I/O, like scrub,
1359from monopolizing the device, no more than
1360.Sy zfs_vdev_nia_credit operations can be sent
1361while there are outstanding incomplete interactive operations.
1362This enforced wait ensures the HDD services the interactive I/O
1363within a reasonable amount of time.
1364.No See Sx ZFS I/O SCHEDULER .
1365.
1366.It Sy zfs_vdev_queue_depth_pct Ns = Ns Sy 1000 Ns % Pq uint
1367Maximum number of queued allocations per top-level vdev expressed as
1368a percentage of
1369.Sy zfs_vdev_async_write_max_active ,
1370which allows the system to detect devices that are more capable
1371of handling allocations and to allocate more blocks to those devices.
1372This allows for dynamic allocation distribution when devices are imbalanced,
1373as fuller devices will tend to be slower than empty devices.
1374.Pp
1375Also see
1376.Sy zio_dva_throttle_enabled .
1377.
1378.It Sy zfs_vdev_def_queue_depth Ns = Ns Sy 32 Pq uint
1379Default queue depth for each vdev IO allocator.
1380Higher values allow for better coalescing of sequential writes before sending
1381them to the disk, but can increase transaction commit times.
1382.
1383.It Sy zfs_vdev_failfast_mask Ns = Ns Sy 1 Pq uint
1384Defines if the driver should retire on a given error type.
1385The following options may be bitwise-ored together:
1386.TS
1387box;
1388lbz r l l .
1389	Value	Name	Description
1390_
1391	1	Device	No driver retries on device errors
1392	2	Transport	No driver retries on transport errors.
1393	4	Driver	No driver retries on driver errors.
1394.TE
1395.
1396.It Sy zfs_vdev_disk_max_segs Ns = Ns Sy 0 Pq uint
1397Maximum number of segments to add to a BIO (min 4).
1398If this is higher than the maximum allowed by the device queue or the kernel
1399itself, it will be clamped.
1400Setting it to zero will cause the kernel's ideal size to be used.
1401This parameter only applies on Linux.
1402This parameter is ignored if
1403.Sy zfs_vdev_disk_classic Ns = Ns Sy 1 .
1404.
1405.It Sy zfs_vdev_disk_classic Ns = Ns Sy 0 Ns | Ns 1 Pq uint
1406If set to 1, OpenZFS will submit IO to Linux using the method it used in 2.2
1407and earlier.
1408This "classic" method has known issues with highly fragmented IO requests and
1409is slower on many workloads, but it has been in use for many years and is known
1410to be very stable.
1411If you set this parameter, please also open a bug report why you did so,
1412including the workload involved and any error messages.
1413.Pp
1414This parameter and the classic submission method will be removed once we have
1415total confidence in the new method.
1416.Pp
1417This parameter only applies on Linux, and can only be set at module load time.
1418.
1419.It Sy zfs_expire_snapshot Ns = Ns Sy 300 Ns s Pq int
1420Time before expiring
1421.Pa .zfs/snapshot .
1422.
1423.It Sy zfs_admin_snapshot Ns = Ns Sy 0 Ns | Ns 1 Pq int
1424Allow the creation, removal, or renaming of entries in the
1425.Sy .zfs/snapshot
1426directory to cause the creation, destruction, or renaming of snapshots.
1427When enabled, this functionality works both locally and over NFS exports
1428which have the
1429.Em no_root_squash
1430option set.
1431.
1432.It Sy zfs_flags Ns = Ns Sy 0 Pq int
1433Set additional debugging flags.
1434The following flags may be bitwise-ored together:
1435.TS
1436box;
1437lbz r l l .
1438	Value	Name	Description
1439_
1440	1	ZFS_DEBUG_DPRINTF	Enable dprintf entries in the debug log.
1441*	2	ZFS_DEBUG_DBUF_VERIFY	Enable extra dbuf verifications.
1442*	4	ZFS_DEBUG_DNODE_VERIFY	Enable extra dnode verifications.
1443	8	ZFS_DEBUG_SNAPNAMES	Enable snapshot name verification.
1444*	16	ZFS_DEBUG_MODIFY	Check for illegally modified ARC buffers.
1445	64	ZFS_DEBUG_ZIO_FREE	Enable verification of block frees.
1446	128	ZFS_DEBUG_HISTOGRAM_VERIFY	Enable extra spacemap histogram verifications.
1447	256	ZFS_DEBUG_METASLAB_VERIFY	Verify space accounting on disk matches in-memory \fBrange_trees\fP.
1448	512	ZFS_DEBUG_SET_ERROR	Enable \fBSET_ERROR\fP and dprintf entries in the debug log.
1449	1024	ZFS_DEBUG_INDIRECT_REMAP	Verify split blocks created by device removal.
1450	2048	ZFS_DEBUG_TRIM	Verify TRIM ranges are always within the allocatable range tree.
1451	4096	ZFS_DEBUG_LOG_SPACEMAP	Verify that the log summary is consistent with the spacemap log
1452			       and enable \fBzfs_dbgmsgs\fP for metaslab loading and flushing.
1453.TE
1454.Sy \& * No Requires debug build .
1455.
1456.It Sy zfs_btree_verify_intensity Ns = Ns Sy 0 Pq uint
1457Enables btree verification.
1458The following settings are culminative:
1459.TS
1460box;
1461lbz r l l .
1462	Value	Description
1463
1464	1	Verify height.
1465	2	Verify pointers from children to parent.
1466	3	Verify element counts.
1467	4	Verify element order. (expensive)
1468*	5	Verify unused memory is poisoned. (expensive)
1469.TE
1470.Sy \& * No Requires debug build .
1471.
1472.It Sy zfs_free_leak_on_eio Ns = Ns Sy 0 Ns | Ns 1 Pq int
1473If destroy encounters an
1474.Sy EIO
1475while reading metadata (e.g. indirect blocks),
1476space referenced by the missing metadata can not be freed.
1477Normally this causes the background destroy to become "stalled",
1478as it is unable to make forward progress.
1479While in this stalled state, all remaining space to free
1480from the error-encountering filesystem is "temporarily leaked".
1481Set this flag to cause it to ignore the
1482.Sy EIO ,
1483permanently leak the space from indirect blocks that can not be read,
1484and continue to free everything else that it can.
1485.Pp
1486The default "stalling" behavior is useful if the storage partially
1487fails (i.e. some but not all I/O operations fail), and then later recovers.
1488In this case, we will be able to continue pool operations while it is
1489partially failed, and when it recovers, we can continue to free the
1490space, with no leaks.
1491Note, however, that this case is actually fairly rare.
1492.Pp
1493Typically pools either
1494.Bl -enum -compact -offset 4n -width "1."
1495.It
1496fail completely (but perhaps temporarily,
1497e.g. due to a top-level vdev going offline), or
1498.It
1499have localized, permanent errors (e.g. disk returns the wrong data
1500due to bit flip or firmware bug).
1501.El
1502In the former case, this setting does not matter because the
1503pool will be suspended and the sync thread will not be able to make
1504forward progress regardless.
1505In the latter, because the error is permanent, the best we can do
1506is leak the minimum amount of space,
1507which is what setting this flag will do.
1508It is therefore reasonable for this flag to normally be set,
1509but we chose the more conservative approach of not setting it,
1510so that there is no possibility of
1511leaking space in the "partial temporary" failure case.
1512.
1513.It Sy zfs_free_min_time_ms Ns = Ns Sy 1000 Ns ms Po 1s Pc Pq uint
1514During a
1515.Nm zfs Cm destroy
1516operation using the
1517.Sy async_destroy
1518feature,
1519a minimum of this much time will be spent working on freeing blocks per TXG.
1520.
1521.It Sy zfs_obsolete_min_time_ms Ns = Ns Sy 500 Ns ms Pq uint
1522Similar to
1523.Sy zfs_free_min_time_ms ,
1524but for cleanup of old indirection records for removed vdevs.
1525.
1526.It Sy zfs_immediate_write_sz Ns = Ns Sy 32768 Ns B Po 32 KiB Pc Pq s64
1527Largest data block to write to the ZIL.
1528Larger blocks will be treated as if the dataset being written to had the
1529.Sy logbias Ns = Ns Sy throughput
1530property set.
1531.
1532.It Sy zfs_initialize_value Ns = Ns Sy 16045690984833335022 Po 0xDEADBEEFDEADBEEE Pc Pq u64
1533Pattern written to vdev free space by
1534.Xr zpool-initialize 8 .
1535.
1536.It Sy zfs_initialize_chunk_size Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq u64
1537Size of writes used by
1538.Xr zpool-initialize 8 .
1539This option is used by the test suite.
1540.
1541.It Sy zfs_livelist_max_entries Ns = Ns Sy 500000 Po 5*10^5 Pc Pq u64
1542The threshold size (in block pointers) at which we create a new sub-livelist.
1543Larger sublists are more costly from a memory perspective but the fewer
1544sublists there are, the lower the cost of insertion.
1545.
1546.It Sy zfs_livelist_min_percent_shared Ns = Ns Sy 75 Ns % Pq int
1547If the amount of shared space between a snapshot and its clone drops below
1548this threshold, the clone turns off the livelist and reverts to the old
1549deletion method.
1550This is in place because livelists no long give us a benefit
1551once a clone has been overwritten enough.
1552.
1553.It Sy zfs_livelist_condense_new_alloc Ns = Ns Sy 0 Pq int
1554Incremented each time an extra ALLOC blkptr is added to a livelist entry while
1555it is being condensed.
1556This option is used by the test suite to track race conditions.
1557.
1558.It Sy zfs_livelist_condense_sync_cancel Ns = Ns Sy 0 Pq int
1559Incremented each time livelist condensing is canceled while in
1560.Fn spa_livelist_condense_sync .
1561This option is used by the test suite to track race conditions.
1562.
1563.It Sy zfs_livelist_condense_sync_pause Ns = Ns Sy 0 Ns | Ns 1 Pq int
1564When set, the livelist condense process pauses indefinitely before
1565executing the synctask \(em
1566.Fn spa_livelist_condense_sync .
1567This option is used by the test suite to trigger race conditions.
1568.
1569.It Sy zfs_livelist_condense_zthr_cancel Ns = Ns Sy 0 Pq int
1570Incremented each time livelist condensing is canceled while in
1571.Fn spa_livelist_condense_cb .
1572This option is used by the test suite to track race conditions.
1573.
1574.It Sy zfs_livelist_condense_zthr_pause Ns = Ns Sy 0 Ns | Ns 1 Pq int
1575When set, the livelist condense process pauses indefinitely before
1576executing the open context condensing work in
1577.Fn spa_livelist_condense_cb .
1578This option is used by the test suite to trigger race conditions.
1579.
1580.It Sy zfs_lua_max_instrlimit Ns = Ns Sy 100000000 Po 10^8 Pc Pq u64
1581The maximum execution time limit that can be set for a ZFS channel program,
1582specified as a number of Lua instructions.
1583.
1584.It Sy zfs_lua_max_memlimit Ns = Ns Sy 104857600 Po 100 MiB Pc Pq u64
1585The maximum memory limit that can be set for a ZFS channel program, specified
1586in bytes.
1587.
1588.It Sy zfs_max_dataset_nesting Ns = Ns Sy 50 Pq int
1589The maximum depth of nested datasets.
1590This value can be tuned temporarily to
1591fix existing datasets that exceed the predefined limit.
1592.
1593.It Sy zfs_max_log_walking Ns = Ns Sy 5 Pq u64
1594The number of past TXGs that the flushing algorithm of the log spacemap
1595feature uses to estimate incoming log blocks.
1596.
1597.It Sy zfs_max_logsm_summary_length Ns = Ns Sy 10 Pq u64
1598Maximum number of rows allowed in the summary of the spacemap log.
1599.
1600.It Sy zfs_max_recordsize Ns = Ns Sy 16777216 Po 16 MiB Pc Pq uint
1601We currently support block sizes from
1602.Em 512 Po 512 B Pc No to Em 16777216 Po 16 MiB Pc .
1603The benefits of larger blocks, and thus larger I/O,
1604need to be weighed against the cost of COWing a giant block to modify one byte.
1605Additionally, very large blocks can have an impact on I/O latency,
1606and also potentially on the memory allocator.
1607Therefore, we formerly forbade creating blocks larger than 1M.
1608Larger blocks could be created by changing it,
1609and pools with larger blocks can always be imported and used,
1610regardless of this setting.
1611.
1612.It Sy zfs_allow_redacted_dataset_mount Ns = Ns Sy 0 Ns | Ns 1 Pq int
1613Allow datasets received with redacted send/receive to be mounted.
1614Normally disabled because these datasets may be missing key data.
1615.
1616.It Sy zfs_min_metaslabs_to_flush Ns = Ns Sy 1 Pq u64
1617Minimum number of metaslabs to flush per dirty TXG.
1618.
1619.It Sy zfs_metaslab_fragmentation_threshold Ns = Ns Sy 70 Ns % Pq uint
1620Allow metaslabs to keep their active state as long as their fragmentation
1621percentage is no more than this value.
1622An active metaslab that exceeds this threshold
1623will no longer keep its active status allowing better metaslabs to be selected.
1624.
1625.It Sy zfs_mg_fragmentation_threshold Ns = Ns Sy 95 Ns % Pq uint
1626Metaslab groups are considered eligible for allocations if their
1627fragmentation metric (measured as a percentage) is less than or equal to
1628this value.
1629If a metaslab group exceeds this threshold then it will be
1630skipped unless all metaslab groups within the metaslab class have also
1631crossed this threshold.
1632.
1633.It Sy zfs_mg_noalloc_threshold Ns = Ns Sy 0 Ns % Pq uint
1634Defines a threshold at which metaslab groups should be eligible for allocations.
1635The value is expressed as a percentage of free space
1636beyond which a metaslab group is always eligible for allocations.
1637If a metaslab group's free space is less than or equal to the
1638threshold, the allocator will avoid allocating to that group
1639unless all groups in the pool have reached the threshold.
1640Once all groups have reached the threshold, all groups are allowed to accept
1641allocations.
1642The default value of
1643.Sy 0
1644disables the feature and causes all metaslab groups to be eligible for
1645allocations.
1646.Pp
1647This parameter allows one to deal with pools having heavily imbalanced
1648vdevs such as would be the case when a new vdev has been added.
1649Setting the threshold to a non-zero percentage will stop allocations
1650from being made to vdevs that aren't filled to the specified percentage
1651and allow lesser filled vdevs to acquire more allocations than they
1652otherwise would under the old
1653.Sy zfs_mg_alloc_failures
1654facility.
1655.
1656.It Sy zfs_ddt_data_is_special Ns = Ns Sy 1 Ns | Ns 0 Pq int
1657If enabled, ZFS will place DDT data into the special allocation class.
1658.
1659.It Sy zfs_user_indirect_is_special Ns = Ns Sy 1 Ns | Ns 0 Pq int
1660If enabled, ZFS will place user data indirect blocks
1661into the special allocation class.
1662.
1663.It Sy zfs_multihost_history Ns = Ns Sy 0 Pq uint
1664Historical statistics for this many latest multihost updates will be available
1665in
1666.Pa /proc/spl/kstat/zfs/ Ns Ao Ar pool Ac Ns Pa /multihost .
1667.
1668.It Sy zfs_multihost_interval Ns = Ns Sy 1000 Ns ms Po 1 s Pc Pq u64
1669Used to control the frequency of multihost writes which are performed when the
1670.Sy multihost
1671pool property is on.
1672This is one of the factors used to determine the
1673length of the activity check during import.
1674.Pp
1675The multihost write period is
1676.Sy zfs_multihost_interval No / Sy leaf-vdevs .
1677On average a multihost write will be issued for each leaf vdev
1678every
1679.Sy zfs_multihost_interval
1680milliseconds.
1681In practice, the observed period can vary with the I/O load
1682and this observed value is the delay which is stored in the uberblock.
1683.
1684.It Sy zfs_multihost_import_intervals Ns = Ns Sy 20 Pq uint
1685Used to control the duration of the activity test on import.
1686Smaller values of
1687.Sy zfs_multihost_import_intervals
1688will reduce the import time but increase
1689the risk of failing to detect an active pool.
1690The total activity check time is never allowed to drop below one second.
1691.Pp
1692On import the activity check waits a minimum amount of time determined by
1693.Sy zfs_multihost_interval No \(mu Sy zfs_multihost_import_intervals ,
1694or the same product computed on the host which last had the pool imported,
1695whichever is greater.
1696The activity check time may be further extended if the value of MMP
1697delay found in the best uberblock indicates actual multihost updates happened
1698at longer intervals than
1699.Sy zfs_multihost_interval .
1700A minimum of
1701.Em 100 ms
1702is enforced.
1703.Pp
1704.Sy 0 No is equivalent to Sy 1 .
1705.
1706.It Sy zfs_multihost_fail_intervals Ns = Ns Sy 10 Pq uint
1707Controls the behavior of the pool when multihost write failures or delays are
1708detected.
1709.Pp
1710When
1711.Sy 0 ,
1712multihost write failures or delays are ignored.
1713The failures will still be reported to the ZED which depending on
1714its configuration may take action such as suspending the pool or offlining a
1715device.
1716.Pp
1717Otherwise, the pool will be suspended if
1718.Sy zfs_multihost_fail_intervals No \(mu Sy zfs_multihost_interval
1719milliseconds pass without a successful MMP write.
1720This guarantees the activity test will see MMP writes if the pool is imported.
1721.Sy 1 No is equivalent to Sy 2 ;
1722this is necessary to prevent the pool from being suspended
1723due to normal, small I/O latency variations.
1724.
1725.It Sy zfs_no_scrub_io Ns = Ns Sy 0 Ns | Ns 1 Pq int
1726Set to disable scrub I/O.
1727This results in scrubs not actually scrubbing data and
1728simply doing a metadata crawl of the pool instead.
1729.
1730.It Sy zfs_no_scrub_prefetch Ns = Ns Sy 0 Ns | Ns 1 Pq int
1731Set to disable block prefetching for scrubs.
1732.
1733.It Sy zfs_nocacheflush Ns = Ns Sy 0 Ns | Ns 1 Pq int
1734Disable cache flush operations on disks when writing.
1735Setting this will cause pool corruption on power loss
1736if a volatile out-of-order write cache is enabled.
1737.
1738.It Sy zfs_nopwrite_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
1739Allow no-operation writes.
1740The occurrence of nopwrites will further depend on other pool properties
1741.Pq i.a. the checksumming and compression algorithms .
1742.
1743.It Sy zfs_dmu_offset_next_sync Ns = Ns Sy 1 Ns | Ns 0 Pq int
1744Enable forcing TXG sync to find holes.
1745When enabled forces ZFS to sync data when
1746.Sy SEEK_HOLE No or Sy SEEK_DATA
1747flags are used allowing holes in a file to be accurately reported.
1748When disabled holes will not be reported in recently dirtied files.
1749.
1750.It Sy zfs_pd_bytes_max Ns = Ns Sy 52428800 Ns B Po 50 MiB Pc Pq int
1751The number of bytes which should be prefetched during a pool traversal, like
1752.Nm zfs Cm send
1753or other data crawling operations.
1754.
1755.It Sy zfs_traverse_indirect_prefetch_limit Ns = Ns Sy 32 Pq uint
1756The number of blocks pointed by indirect (non-L0) block which should be
1757prefetched during a pool traversal, like
1758.Nm zfs Cm send
1759or other data crawling operations.
1760.
1761.It Sy zfs_per_txg_dirty_frees_percent Ns = Ns Sy 30 Ns % Pq u64
1762Control percentage of dirtied indirect blocks from frees allowed into one TXG.
1763After this threshold is crossed, additional frees will wait until the next TXG.
1764.Sy 0 No disables this throttle .
1765.
1766.It Sy zfs_prefetch_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
1767Disable predictive prefetch.
1768Note that it leaves "prescient" prefetch
1769.Pq for, e.g., Nm zfs Cm send
1770intact.
1771Unlike predictive prefetch, prescient prefetch never issues I/O
1772that ends up not being needed, so it can't hurt performance.
1773.
1774.It Sy zfs_qat_checksum_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
1775Disable QAT hardware acceleration for SHA256 checksums.
1776May be unset after the ZFS modules have been loaded to initialize the QAT
1777hardware as long as support is compiled in and the QAT driver is present.
1778.
1779.It Sy zfs_qat_compress_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
1780Disable QAT hardware acceleration for gzip compression.
1781May be unset after the ZFS modules have been loaded to initialize the QAT
1782hardware as long as support is compiled in and the QAT driver is present.
1783.
1784.It Sy zfs_qat_encrypt_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
1785Disable QAT hardware acceleration for AES-GCM encryption.
1786May be unset after the ZFS modules have been loaded to initialize the QAT
1787hardware as long as support is compiled in and the QAT driver is present.
1788.
1789.It Sy zfs_vnops_read_chunk_size Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq u64
1790Bytes to read per chunk.
1791.
1792.It Sy zfs_read_history Ns = Ns Sy 0 Pq uint
1793Historical statistics for this many latest reads will be available in
1794.Pa /proc/spl/kstat/zfs/ Ns Ao Ar pool Ac Ns Pa /reads .
1795.
1796.It Sy zfs_read_history_hits Ns = Ns Sy 0 Ns | Ns 1 Pq int
1797Include cache hits in read history
1798.
1799.It Sy zfs_rebuild_max_segment Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq u64
1800Maximum read segment size to issue when sequentially resilvering a
1801top-level vdev.
1802.
1803.It Sy zfs_rebuild_scrub_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
1804Automatically start a pool scrub when the last active sequential resilver
1805completes in order to verify the checksums of all blocks which have been
1806resilvered.
1807This is enabled by default and strongly recommended.
1808.
1809.It Sy zfs_rebuild_vdev_limit Ns = Ns Sy 67108864 Ns B Po 64 MiB Pc Pq u64
1810Maximum amount of I/O that can be concurrently issued for a sequential
1811resilver per leaf device, given in bytes.
1812.
1813.It Sy zfs_reconstruct_indirect_combinations_max Ns = Ns Sy 4096 Pq int
1814If an indirect split block contains more than this many possible unique
1815combinations when being reconstructed, consider it too computationally
1816expensive to check them all.
1817Instead, try at most this many randomly selected
1818combinations each time the block is accessed.
1819This allows all segment copies to participate fairly
1820in the reconstruction when all combinations
1821cannot be checked and prevents repeated use of one bad copy.
1822.
1823.It Sy zfs_recover Ns = Ns Sy 0 Ns | Ns 1 Pq int
1824Set to attempt to recover from fatal errors.
1825This should only be used as a last resort,
1826as it typically results in leaked space, or worse.
1827.
1828.It Sy zfs_removal_ignore_errors Ns = Ns Sy 0 Ns | Ns 1 Pq int
1829Ignore hard I/O errors during device removal.
1830When set, if a device encounters a hard I/O error during the removal process
1831the removal will not be cancelled.
1832This can result in a normally recoverable block becoming permanently damaged
1833and is hence not recommended.
1834This should only be used as a last resort when the
1835pool cannot be returned to a healthy state prior to removing the device.
1836.
1837.It Sy zfs_removal_suspend_progress Ns = Ns Sy 0 Ns | Ns 1 Pq uint
1838This is used by the test suite so that it can ensure that certain actions
1839happen while in the middle of a removal.
1840.
1841.It Sy zfs_remove_max_segment Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq uint
1842The largest contiguous segment that we will attempt to allocate when removing
1843a device.
1844If there is a performance problem with attempting to allocate large blocks,
1845consider decreasing this.
1846The default value is also the maximum.
1847.
1848.It Sy zfs_resilver_disable_defer Ns = Ns Sy 0 Ns | Ns 1 Pq int
1849Ignore the
1850.Sy resilver_defer
1851feature, causing an operation that would start a resilver to
1852immediately restart the one in progress.
1853.
1854.It Sy zfs_resilver_min_time_ms Ns = Ns Sy 3000 Ns ms Po 3 s Pc Pq uint
1855Resilvers are processed by the sync thread.
1856While resilvering, it will spend at least this much time
1857working on a resilver between TXG flushes.
1858.
1859.It Sy zfs_scan_ignore_errors Ns = Ns Sy 0 Ns | Ns 1 Pq int
1860If set, remove the DTL (dirty time list) upon completion of a pool scan (scrub),
1861even if there were unrepairable errors.
1862Intended to be used during pool repair or recovery to
1863stop resilvering when the pool is next imported.
1864.
1865.It Sy zfs_scrub_after_expand Ns = Ns Sy 1 Ns | Ns 0 Pq int
1866Automatically start a pool scrub after a RAIDZ expansion completes
1867in order to verify the checksums of all blocks which have been
1868copied during the expansion.
1869This is enabled by default and strongly recommended.
1870.
1871.It Sy zfs_scrub_min_time_ms Ns = Ns Sy 1000 Ns ms Po 1 s Pc Pq uint
1872Scrubs are processed by the sync thread.
1873While scrubbing, it will spend at least this much time
1874working on a scrub between TXG flushes.
1875.
1876.It Sy zfs_scrub_error_blocks_per_txg Ns = Ns Sy 4096 Pq uint
1877Error blocks to be scrubbed in one txg.
1878.
1879.It Sy zfs_scan_checkpoint_intval Ns = Ns Sy 7200 Ns s Po 2 hour Pc Pq uint
1880To preserve progress across reboots, the sequential scan algorithm periodically
1881needs to stop metadata scanning and issue all the verification I/O to disk.
1882The frequency of this flushing is determined by this tunable.
1883.
1884.It Sy zfs_scan_fill_weight Ns = Ns Sy 3 Pq uint
1885This tunable affects how scrub and resilver I/O segments are ordered.
1886A higher number indicates that we care more about how filled in a segment is,
1887while a lower number indicates we care more about the size of the extent without
1888considering the gaps within a segment.
1889This value is only tunable upon module insertion.
1890Changing the value afterwards will have no effect on scrub or resilver
1891performance.
1892.
1893.It Sy zfs_scan_issue_strategy Ns = Ns Sy 0 Pq uint
1894Determines the order that data will be verified while scrubbing or resilvering:
1895.Bl -tag -compact -offset 4n -width "a"
1896.It Sy 1
1897Data will be verified as sequentially as possible, given the
1898amount of memory reserved for scrubbing
1899.Pq see Sy zfs_scan_mem_lim_fact .
1900This may improve scrub performance if the pool's data is very fragmented.
1901.It Sy 2
1902The largest mostly-contiguous chunk of found data will be verified first.
1903By deferring scrubbing of small segments, we may later find adjacent data
1904to coalesce and increase the segment size.
1905.It Sy 0
1906.No Use strategy Sy 1 No during normal verification
1907.No and strategy Sy 2 No while taking a checkpoint .
1908.El
1909.
1910.It Sy zfs_scan_legacy Ns = Ns Sy 0 Ns | Ns 1 Pq int
1911If unset, indicates that scrubs and resilvers will gather metadata in
1912memory before issuing sequential I/O.
1913Otherwise indicates that the legacy algorithm will be used,
1914where I/O is initiated as soon as it is discovered.
1915Unsetting will not affect scrubs or resilvers that are already in progress.
1916.
1917.It Sy zfs_scan_max_ext_gap Ns = Ns Sy 2097152 Ns B Po 2 MiB Pc Pq int
1918Sets the largest gap in bytes between scrub/resilver I/O operations
1919that will still be considered sequential for sorting purposes.
1920Changing this value will not
1921affect scrubs or resilvers that are already in progress.
1922.
1923.It Sy zfs_scan_mem_lim_fact Ns = Ns Sy 20 Ns ^-1 Pq uint
1924Maximum fraction of RAM used for I/O sorting by sequential scan algorithm.
1925This tunable determines the hard limit for I/O sorting memory usage.
1926When the hard limit is reached we stop scanning metadata and start issuing
1927data verification I/O.
1928This is done until we get below the soft limit.
1929.
1930.It Sy zfs_scan_mem_lim_soft_fact Ns = Ns Sy 20 Ns ^-1 Pq uint
1931The fraction of the hard limit used to determined the soft limit for I/O sorting
1932by the sequential scan algorithm.
1933When we cross this limit from below no action is taken.
1934When we cross this limit from above it is because we are issuing verification
1935I/O.
1936In this case (unless the metadata scan is done) we stop issuing verification I/O
1937and start scanning metadata again until we get to the hard limit.
1938.
1939.It Sy zfs_scan_report_txgs Ns = Ns Sy 0 Ns | Ns 1 Pq uint
1940When reporting resilver throughput and estimated completion time use the
1941performance observed over roughly the last
1942.Sy zfs_scan_report_txgs
1943TXGs.
1944When set to zero performance is calculated over the time between checkpoints.
1945.
1946.It Sy zfs_scan_strict_mem_lim Ns = Ns Sy 0 Ns | Ns 1 Pq int
1947Enforce tight memory limits on pool scans when a sequential scan is in progress.
1948When disabled, the memory limit may be exceeded by fast disks.
1949.
1950.It Sy zfs_scan_suspend_progress Ns = Ns Sy 0 Ns | Ns 1 Pq int
1951Freezes a scrub/resilver in progress without actually pausing it.
1952Intended for testing/debugging.
1953.
1954.It Sy zfs_scan_vdev_limit Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq int
1955Maximum amount of data that can be concurrently issued at once for scrubs and
1956resilvers per leaf device, given in bytes.
1957.
1958.It Sy zfs_send_corrupt_data Ns = Ns Sy 0 Ns | Ns 1 Pq int
1959Allow sending of corrupt data (ignore read/checksum errors when sending).
1960.
1961.It Sy zfs_send_unmodified_spill_blocks Ns = Ns Sy 1 Ns | Ns 0 Pq int
1962Include unmodified spill blocks in the send stream.
1963Under certain circumstances, previous versions of ZFS could incorrectly
1964remove the spill block from an existing object.
1965Including unmodified copies of the spill blocks creates a backwards-compatible
1966stream which will recreate a spill block if it was incorrectly removed.
1967.
1968.It Sy zfs_send_no_prefetch_queue_ff Ns = Ns Sy 20 Ns ^\-1 Pq uint
1969The fill fraction of the
1970.Nm zfs Cm send
1971internal queues.
1972The fill fraction controls the timing with which internal threads are woken up.
1973.
1974.It Sy zfs_send_no_prefetch_queue_length Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq uint
1975The maximum number of bytes allowed in
1976.Nm zfs Cm send Ns 's
1977internal queues.
1978.
1979.It Sy zfs_send_queue_ff Ns = Ns Sy 20 Ns ^\-1 Pq uint
1980The fill fraction of the
1981.Nm zfs Cm send
1982prefetch queue.
1983The fill fraction controls the timing with which internal threads are woken up.
1984.
1985.It Sy zfs_send_queue_length Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq uint
1986The maximum number of bytes allowed that will be prefetched by
1987.Nm zfs Cm send .
1988This value must be at least twice the maximum block size in use.
1989.
1990.It Sy zfs_recv_queue_ff Ns = Ns Sy 20 Ns ^\-1 Pq uint
1991The fill fraction of the
1992.Nm zfs Cm receive
1993queue.
1994The fill fraction controls the timing with which internal threads are woken up.
1995.
1996.It Sy zfs_recv_queue_length Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq uint
1997The maximum number of bytes allowed in the
1998.Nm zfs Cm receive
1999queue.
2000This value must be at least twice the maximum block size in use.
2001.
2002.It Sy zfs_recv_write_batch_size Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq uint
2003The maximum amount of data, in bytes, that
2004.Nm zfs Cm receive
2005will write in one DMU transaction.
2006This is the uncompressed size, even when receiving a compressed send stream.
2007This setting will not reduce the write size below a single block.
2008Capped at a maximum of
2009.Sy 32 MiB .
2010.
2011.It Sy zfs_recv_best_effort_corrective Ns = Ns Sy 0 Pq int
2012When this variable is set to non-zero a corrective receive:
2013.Bl -enum -compact -offset 4n -width "1."
2014.It
2015Does not enforce the restriction of source & destination snapshot GUIDs
2016matching.
2017.It
2018If there is an error during healing, the healing receive is not
2019terminated instead it moves on to the next record.
2020.El
2021.
2022.It Sy zfs_override_estimate_recordsize Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2023Setting this variable overrides the default logic for estimating block
2024sizes when doing a
2025.Nm zfs Cm send .
2026The default heuristic is that the average block size
2027will be the current recordsize.
2028Override this value if most data in your dataset is not of that size
2029and you require accurate zfs send size estimates.
2030.
2031.It Sy zfs_sync_pass_deferred_free Ns = Ns Sy 2 Pq uint
2032Flushing of data to disk is done in passes.
2033Defer frees starting in this pass.
2034.
2035.It Sy zfs_spa_discard_memory_limit Ns = Ns Sy 16777216 Ns B Po 16 MiB Pc Pq int
2036Maximum memory used for prefetching a checkpoint's space map on each
2037vdev while discarding the checkpoint.
2038.
2039.It Sy zfs_special_class_metadata_reserve_pct Ns = Ns Sy 25 Ns % Pq uint
2040Only allow small data blocks to be allocated on the special and dedup vdev
2041types when the available free space percentage on these vdevs exceeds this
2042value.
2043This ensures reserved space is available for pool metadata as the
2044special vdevs approach capacity.
2045.
2046.It Sy zfs_sync_pass_dont_compress Ns = Ns Sy 8 Pq uint
2047Starting in this sync pass, disable compression (including of metadata).
2048With the default setting, in practice, we don't have this many sync passes,
2049so this has no effect.
2050.Pp
2051The original intent was that disabling compression would help the sync passes
2052to converge.
2053However, in practice, disabling compression increases
2054the average number of sync passes; because when we turn compression off,
2055many blocks' size will change, and thus we have to re-allocate
2056(not overwrite) them.
2057It also increases the number of
2058.Em 128 KiB
2059allocations (e.g. for indirect blocks and spacemaps)
2060because these will not be compressed.
2061The
2062.Em 128 KiB
2063allocations are especially detrimental to performance
2064on highly fragmented systems, which may have very few free segments of this
2065size,
2066and may need to load new metaslabs to satisfy these allocations.
2067.
2068.It Sy zfs_sync_pass_rewrite Ns = Ns Sy 2 Pq uint
2069Rewrite new block pointers starting in this pass.
2070.
2071.It Sy zfs_trim_extent_bytes_max Ns = Ns Sy 134217728 Ns B Po 128 MiB Pc Pq uint
2072Maximum size of TRIM command.
2073Larger ranges will be split into chunks no larger than this value before
2074issuing.
2075.
2076.It Sy zfs_trim_extent_bytes_min Ns = Ns Sy 32768 Ns B Po 32 KiB Pc Pq uint
2077Minimum size of TRIM commands.
2078TRIM ranges smaller than this will be skipped,
2079unless they're part of a larger range which was chunked.
2080This is done because it's common for these small TRIMs
2081to negatively impact overall performance.
2082.
2083.It Sy zfs_trim_metaslab_skip Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2084Skip uninitialized metaslabs during the TRIM process.
2085This option is useful for pools constructed from large thinly-provisioned
2086devices
2087where TRIM operations are slow.
2088As a pool ages, an increasing fraction of the pool's metaslabs
2089will be initialized, progressively degrading the usefulness of this option.
2090This setting is stored when starting a manual TRIM and will
2091persist for the duration of the requested TRIM.
2092.
2093.It Sy zfs_trim_queue_limit Ns = Ns Sy 10 Pq uint
2094Maximum number of queued TRIMs outstanding per leaf vdev.
2095The number of concurrent TRIM commands issued to the device is controlled by
2096.Sy zfs_vdev_trim_min_active No and Sy zfs_vdev_trim_max_active .
2097.
2098.It Sy zfs_trim_txg_batch Ns = Ns Sy 32 Pq uint
2099The number of transaction groups' worth of frees which should be aggregated
2100before TRIM operations are issued to the device.
2101This setting represents a trade-off between issuing larger,
2102more efficient TRIM operations and the delay
2103before the recently trimmed space is available for use by the device.
2104.Pp
2105Increasing this value will allow frees to be aggregated for a longer time.
2106This will result is larger TRIM operations and potentially increased memory
2107usage.
2108Decreasing this value will have the opposite effect.
2109The default of
2110.Sy 32
2111was determined to be a reasonable compromise.
2112.
2113.It Sy zfs_txg_history Ns = Ns Sy 0 Pq uint
2114Historical statistics for this many latest TXGs will be available in
2115.Pa /proc/spl/kstat/zfs/ Ns Ao Ar pool Ac Ns Pa /TXGs .
2116.
2117.It Sy zfs_txg_timeout Ns = Ns Sy 5 Ns s Pq uint
2118Flush dirty data to disk at least every this many seconds (maximum TXG
2119duration).
2120.
2121.It Sy zfs_vdev_aggregation_limit Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq uint
2122Max vdev I/O aggregation size.
2123.
2124.It Sy zfs_vdev_aggregation_limit_non_rotating Ns = Ns Sy 131072 Ns B Po 128 KiB Pc Pq uint
2125Max vdev I/O aggregation size for non-rotating media.
2126.
2127.It Sy zfs_vdev_mirror_rotating_inc Ns = Ns Sy 0 Pq int
2128A number by which the balancing algorithm increments the load calculation for
2129the purpose of selecting the least busy mirror member when an I/O operation
2130immediately follows its predecessor on rotational vdevs
2131for the purpose of making decisions based on load.
2132.
2133.It Sy zfs_vdev_mirror_rotating_seek_inc Ns = Ns Sy 5 Pq int
2134A number by which the balancing algorithm increments the load calculation for
2135the purpose of selecting the least busy mirror member when an I/O operation
2136lacks locality as defined by
2137.Sy zfs_vdev_mirror_rotating_seek_offset .
2138Operations within this that are not immediately following the previous operation
2139are incremented by half.
2140.
2141.It Sy zfs_vdev_mirror_rotating_seek_offset Ns = Ns Sy 1048576 Ns B Po 1 MiB Pc Pq int
2142The maximum distance for the last queued I/O operation in which
2143the balancing algorithm considers an operation to have locality.
2144.No See Sx ZFS I/O SCHEDULER .
2145.
2146.It Sy zfs_vdev_mirror_non_rotating_inc Ns = Ns Sy 0 Pq int
2147A number by which the balancing algorithm increments the load calculation for
2148the purpose of selecting the least busy mirror member on non-rotational vdevs
2149when I/O operations do not immediately follow one another.
2150.
2151.It Sy zfs_vdev_mirror_non_rotating_seek_inc Ns = Ns Sy 1 Pq int
2152A number by which the balancing algorithm increments the load calculation for
2153the purpose of selecting the least busy mirror member when an I/O operation
2154lacks
2155locality as defined by the
2156.Sy zfs_vdev_mirror_rotating_seek_offset .
2157Operations within this that are not immediately following the previous operation
2158are incremented by half.
2159.
2160.It Sy zfs_vdev_read_gap_limit Ns = Ns Sy 32768 Ns B Po 32 KiB Pc Pq uint
2161Aggregate read I/O operations if the on-disk gap between them is within this
2162threshold.
2163.
2164.It Sy zfs_vdev_write_gap_limit Ns = Ns Sy 4096 Ns B Po 4 KiB Pc Pq uint
2165Aggregate write I/O operations if the on-disk gap between them is within this
2166threshold.
2167.
2168.It Sy zfs_vdev_raidz_impl Ns = Ns Sy fastest Pq string
2169Select the raidz parity implementation to use.
2170.Pp
2171Variants that don't depend on CPU-specific features
2172may be selected on module load, as they are supported on all systems.
2173The remaining options may only be set after the module is loaded,
2174as they are available only if the implementations are compiled in
2175and supported on the running system.
2176.Pp
2177Once the module is loaded,
2178.Pa /sys/module/zfs/parameters/zfs_vdev_raidz_impl
2179will show the available options,
2180with the currently selected one enclosed in square brackets.
2181.Pp
2182.TS
2183lb l l .
2184fastest	selected by built-in benchmark
2185original	original implementation
2186scalar	scalar implementation
2187sse2	SSE2 instruction set	64-bit x86
2188ssse3	SSSE3 instruction set	64-bit x86
2189avx2	AVX2 instruction set	64-bit x86
2190avx512f	AVX512F instruction set	64-bit x86
2191avx512bw	AVX512F & AVX512BW instruction sets	64-bit x86
2192aarch64_neon	NEON	Aarch64/64-bit ARMv8
2193aarch64_neonx2	NEON with more unrolling	Aarch64/64-bit ARMv8
2194powerpc_altivec	Altivec	PowerPC
2195.TE
2196.
2197.It Sy zfs_vdev_scheduler Pq charp
2198.Sy DEPRECATED .
2199Prints warning to kernel log for compatibility.
2200.
2201.It Sy zfs_zevent_len_max Ns = Ns Sy 512 Pq uint
2202Max event queue length.
2203Events in the queue can be viewed with
2204.Xr zpool-events 8 .
2205.
2206.It Sy zfs_zevent_retain_max Ns = Ns Sy 2000 Pq int
2207Maximum recent zevent records to retain for duplicate checking.
2208Setting this to
2209.Sy 0
2210disables duplicate detection.
2211.
2212.It Sy zfs_zevent_retain_expire_secs Ns = Ns Sy 900 Ns s Po 15 min Pc Pq int
2213Lifespan for a recent ereport that was retained for duplicate checking.
2214.
2215.It Sy zfs_zil_clean_taskq_maxalloc Ns = Ns Sy 1048576 Pq int
2216The maximum number of taskq entries that are allowed to be cached.
2217When this limit is exceeded transaction records (itxs)
2218will be cleaned synchronously.
2219.
2220.It Sy zfs_zil_clean_taskq_minalloc Ns = Ns Sy 1024 Pq int
2221The number of taskq entries that are pre-populated when the taskq is first
2222created and are immediately available for use.
2223.
2224.It Sy zfs_zil_clean_taskq_nthr_pct Ns = Ns Sy 100 Ns % Pq int
2225This controls the number of threads used by
2226.Sy dp_zil_clean_taskq .
2227The default value of
2228.Sy 100%
2229will create a maximum of one thread per cpu.
2230.
2231.It Sy zil_maxblocksize Ns = Ns Sy 131072 Ns B Po 128 KiB Pc Pq uint
2232This sets the maximum block size used by the ZIL.
2233On very fragmented pools, lowering this
2234.Pq typically to Sy 36 KiB
2235can improve performance.
2236.
2237.It Sy zil_maxcopied Ns = Ns Sy 7680 Ns B Po 7.5 KiB Pc Pq uint
2238This sets the maximum number of write bytes logged via WR_COPIED.
2239It tunes a tradeoff between additional memory copy and possibly worse log
2240space efficiency vs additional range lock/unlock.
2241.
2242.It Sy zil_nocacheflush Ns = Ns Sy 0 Ns | Ns 1 Pq int
2243Disable the cache flush commands that are normally sent to disk by
2244the ZIL after an LWB write has completed.
2245Setting this will cause ZIL corruption on power loss
2246if a volatile out-of-order write cache is enabled.
2247.
2248.It Sy zil_replay_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
2249Disable intent logging replay.
2250Can be disabled for recovery from corrupted ZIL.
2251.
2252.It Sy zil_slog_bulk Ns = Ns Sy 67108864 Ns B Po 64 MiB Pc Pq u64
2253Limit SLOG write size per commit executed with synchronous priority.
2254Any writes above that will be executed with lower (asynchronous) priority
2255to limit potential SLOG device abuse by single active ZIL writer.
2256.
2257.It Sy zfs_zil_saxattr Ns = Ns Sy 1 Ns | Ns 0 Pq int
2258Setting this tunable to zero disables ZIL logging of new
2259.Sy xattr Ns = Ns Sy sa
2260records if the
2261.Sy org.openzfs:zilsaxattr
2262feature is enabled on the pool.
2263This would only be necessary to work around bugs in the ZIL logging or replay
2264code for this record type.
2265The tunable has no effect if the feature is disabled.
2266.
2267.It Sy zfs_embedded_slog_min_ms Ns = Ns Sy 64 Pq uint
2268Usually, one metaslab from each normal-class vdev is dedicated for use by
2269the ZIL to log synchronous writes.
2270However, if there are fewer than
2271.Sy zfs_embedded_slog_min_ms
2272metaslabs in the vdev, this functionality is disabled.
2273This ensures that we don't set aside an unreasonable amount of space for the
2274ZIL.
2275.
2276.It Sy zstd_earlyabort_pass Ns = Ns Sy 1 Pq uint
2277Whether heuristic for detection of incompressible data with zstd levels >= 3
2278using LZ4 and zstd-1 passes is enabled.
2279.
2280.It Sy zstd_abort_size Ns = Ns Sy 131072 Pq uint
2281Minimal uncompressed size (inclusive) of a record before the early abort
2282heuristic will be attempted.
2283.
2284.It Sy zio_deadman_log_all Ns = Ns Sy 0 Ns | Ns 1 Pq int
2285If non-zero, the zio deadman will produce debugging messages
2286.Pq see Sy zfs_dbgmsg_enable
2287for all zios, rather than only for leaf zios possessing a vdev.
2288This is meant to be used by developers to gain
2289diagnostic information for hang conditions which don't involve a mutex
2290or other locking primitive: typically conditions in which a thread in
2291the zio pipeline is looping indefinitely.
2292.
2293.It Sy zio_slow_io_ms Ns = Ns Sy 30000 Ns ms Po 30 s Pc Pq int
2294When an I/O operation takes more than this much time to complete,
2295it's marked as slow.
2296Each slow operation causes a delay zevent.
2297Slow I/O counters can be seen with
2298.Nm zpool Cm status Fl s .
2299.
2300.It Sy zio_dva_throttle_enabled Ns = Ns Sy 1 Ns | Ns 0 Pq int
2301Throttle block allocations in the I/O pipeline.
2302This allows for dynamic allocation distribution when devices are imbalanced.
2303When enabled, the maximum number of pending allocations per top-level vdev
2304is limited by
2305.Sy zfs_vdev_queue_depth_pct .
2306.
2307.It Sy zfs_xattr_compat Ns = Ns 0 Ns | Ns 1 Pq int
2308Control the naming scheme used when setting new xattrs in the user namespace.
2309If
2310.Sy 0
2311.Pq the default on Linux ,
2312user namespace xattr names are prefixed with the namespace, to be backwards
2313compatible with previous versions of ZFS on Linux.
2314If
2315.Sy 1
2316.Pq the default on Fx ,
2317user namespace xattr names are not prefixed, to be backwards compatible with
2318previous versions of ZFS on illumos and
2319.Fx .
2320.Pp
2321Either naming scheme can be read on this and future versions of ZFS, regardless
2322of this tunable, but legacy ZFS on illumos or
2323.Fx
2324are unable to read user namespace xattrs written in the Linux format, and
2325legacy versions of ZFS on Linux are unable to read user namespace xattrs written
2326in the legacy ZFS format.
2327.Pp
2328An existing xattr with the alternate naming scheme is removed when overwriting
2329the xattr so as to not accumulate duplicates.
2330.
2331.It Sy zio_requeue_io_start_cut_in_line Ns = Ns Sy 0 Ns | Ns 1 Pq int
2332Prioritize requeued I/O.
2333.
2334.It Sy zio_taskq_batch_pct Ns = Ns Sy 80 Ns % Pq uint
2335Percentage of online CPUs which will run a worker thread for I/O.
2336These workers are responsible for I/O work such as compression, encryption,
2337checksum and parity calculations.
2338Fractional number of CPUs will be rounded down.
2339.Pp
2340The default value of
2341.Sy 80%
2342was chosen to avoid using all CPUs which can result in
2343latency issues and inconsistent application performance,
2344especially when slower compression and/or checksumming is enabled.
2345Set value only applies to pools imported/created after that.
2346.
2347.It Sy zio_taskq_batch_tpq Ns = Ns Sy 0 Pq uint
2348Number of worker threads per taskq.
2349Higher values improve I/O ordering and CPU utilization,
2350while lower reduce lock contention.
2351Set value only applies to pools imported/created after that.
2352.Pp
2353If
2354.Sy 0 ,
2355generate a system-dependent value close to 6 threads per taskq.
2356Set value only applies to pools imported/created after that.
2357.
2358.It Sy zio_taskq_write_tpq Ns = Ns Sy 16 Pq uint
2359Determines the minumum number of threads per write issue taskq.
2360Higher values improve CPU utilization on high throughput,
2361while lower reduce taskq locks contention on high IOPS.
2362Set value only applies to pools imported/created after that.
2363.
2364.It Sy zio_taskq_read Ns = Ns Sy fixed,1,8 null scale null Pq charp
2365Set the queue and thread configuration for the IO read queues.
2366This is an advanced debugging parameter.
2367Don't change this unless you understand what it does.
2368Set values only apply to pools imported/created after that.
2369.
2370.It Sy zio_taskq_write Ns = Ns Sy sync fixed,1,5 scale fixed,1,5 Pq charp
2371Set the queue and thread configuration for the IO write queues.
2372This is an advanced debugging parameter.
2373Don't change this unless you understand what it does.
2374Set values only apply to pools imported/created after that.
2375.
2376.It Sy zvol_inhibit_dev Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2377Do not create zvol device nodes.
2378This may slightly improve startup time on
2379systems with a very large number of zvols.
2380.
2381.It Sy zvol_major Ns = Ns Sy 230 Pq uint
2382Major number for zvol block devices.
2383.
2384.It Sy zvol_max_discard_blocks Ns = Ns Sy 16384 Pq long
2385Discard (TRIM) operations done on zvols will be done in batches of this
2386many blocks, where block size is determined by the
2387.Sy volblocksize
2388property of a zvol.
2389.
2390.It Sy zvol_prefetch_bytes Ns = Ns Sy 131072 Ns B Po 128 KiB Pc Pq uint
2391When adding a zvol to the system, prefetch this many bytes
2392from the start and end of the volume.
2393Prefetching these regions of the volume is desirable,
2394because they are likely to be accessed immediately by
2395.Xr blkid 8
2396or the kernel partitioner.
2397.
2398.It Sy zvol_request_sync Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2399When processing I/O requests for a zvol, submit them synchronously.
2400This effectively limits the queue depth to
2401.Em 1
2402for each I/O submitter.
2403When unset, requests are handled asynchronously by a thread pool.
2404The number of requests which can be handled concurrently is controlled by
2405.Sy zvol_threads .
2406.Sy zvol_request_sync
2407is ignored when running on a kernel that supports block multiqueue
2408.Pq Li blk-mq .
2409.
2410.It Sy zvol_num_taskqs Ns = Ns Sy 0 Pq uint
2411Number of zvol taskqs.
2412If
2413.Sy 0
2414(the default) then scaling is done internally to prefer 6 threads per taskq.
2415This only applies on Linux.
2416.
2417.It Sy zvol_threads Ns = Ns Sy 0 Pq uint
2418The number of system wide threads to use for processing zvol block IOs.
2419If
2420.Sy 0
2421(the default) then internally set
2422.Sy zvol_threads
2423to the number of CPUs present or 32 (whichever is greater).
2424.
2425.It Sy zvol_blk_mq_threads Ns = Ns Sy 0 Pq uint
2426The number of threads per zvol to use for queuing IO requests.
2427This parameter will only appear if your kernel supports
2428.Li blk-mq
2429and is only read and assigned to a zvol at zvol load time.
2430If
2431.Sy 0
2432(the default) then internally set
2433.Sy zvol_blk_mq_threads
2434to the number of CPUs present.
2435.
2436.It Sy zvol_use_blk_mq Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2437Set to
2438.Sy 1
2439to use the
2440.Li blk-mq
2441API for zvols.
2442Set to
2443.Sy 0
2444(the default) to use the legacy zvol APIs.
2445This setting can give better or worse zvol performance depending on
2446the workload.
2447This parameter will only appear if your kernel supports
2448.Li blk-mq
2449and is only read and assigned to a zvol at zvol load time.
2450.
2451.It Sy zvol_blk_mq_blocks_per_thread Ns = Ns Sy 8 Pq uint
2452If
2453.Sy zvol_use_blk_mq
2454is enabled, then process this number of
2455.Sy volblocksize Ns -sized blocks per zvol thread.
2456This tunable can be use to favor better performance for zvol reads (lower
2457values) or writes (higher values).
2458If set to
2459.Sy 0 ,
2460then the zvol layer will process the maximum number of blocks
2461per thread that it can.
2462This parameter will only appear if your kernel supports
2463.Li blk-mq
2464and is only applied at each zvol's load time.
2465.
2466.It Sy zvol_blk_mq_queue_depth Ns = Ns Sy 0 Pq uint
2467The queue_depth value for the zvol
2468.Li blk-mq
2469interface.
2470This parameter will only appear if your kernel supports
2471.Li blk-mq
2472and is only applied at each zvol's load time.
2473If
2474.Sy 0
2475(the default) then use the kernel's default queue depth.
2476Values are clamped to the kernel's
2477.Dv BLKDEV_MIN_RQ
2478and
2479.Dv BLKDEV_MAX_RQ Ns / Ns Dv BLKDEV_DEFAULT_RQ
2480limits.
2481.
2482.It Sy zvol_volmode Ns = Ns Sy 1 Pq uint
2483Defines zvol block devices behaviour when
2484.Sy volmode Ns = Ns Sy default :
2485.Bl -tag -compact -offset 4n -width "a"
2486.It Sy 1
2487.No equivalent to Sy full
2488.It Sy 2
2489.No equivalent to Sy dev
2490.It Sy 3
2491.No equivalent to Sy none
2492.El
2493.
2494.It Sy zvol_enforce_quotas Ns = Ns Sy 0 Ns | Ns 1 Pq uint
2495Enable strict ZVOL quota enforcement.
2496The strict quota enforcement may have a performance impact.
2497.El
2498.
2499.Sh ZFS I/O SCHEDULER
2500ZFS issues I/O operations to leaf vdevs to satisfy and complete I/O operations.
2501The scheduler determines when and in what order those operations are issued.
2502The scheduler divides operations into five I/O classes,
2503prioritized in the following order: sync read, sync write, async read,
2504async write, and scrub/resilver.
2505Each queue defines the minimum and maximum number of concurrent operations
2506that may be issued to the device.
2507In addition, the device has an aggregate maximum,
2508.Sy zfs_vdev_max_active .
2509Note that the sum of the per-queue minima must not exceed the aggregate maximum.
2510If the sum of the per-queue maxima exceeds the aggregate maximum,
2511then the number of active operations may reach
2512.Sy zfs_vdev_max_active ,
2513in which case no further operations will be issued,
2514regardless of whether all per-queue minima have been met.
2515.Pp
2516For many physical devices, throughput increases with the number of
2517concurrent operations, but latency typically suffers.
2518Furthermore, physical devices typically have a limit
2519at which more concurrent operations have no
2520effect on throughput or can actually cause it to decrease.
2521.Pp
2522The scheduler selects the next operation to issue by first looking for an
2523I/O class whose minimum has not been satisfied.
2524Once all are satisfied and the aggregate maximum has not been hit,
2525the scheduler looks for classes whose maximum has not been satisfied.
2526Iteration through the I/O classes is done in the order specified above.
2527No further operations are issued
2528if the aggregate maximum number of concurrent operations has been hit,
2529or if there are no operations queued for an I/O class that has not hit its
2530maximum.
2531Every time an I/O operation is queued or an operation completes,
2532the scheduler looks for new operations to issue.
2533.Pp
2534In general, smaller
2535.Sy max_active Ns s
2536will lead to lower latency of synchronous operations.
2537Larger
2538.Sy max_active Ns s
2539may lead to higher overall throughput, depending on underlying storage.
2540.Pp
2541The ratio of the queues'
2542.Sy max_active Ns s
2543determines the balance of performance between reads, writes, and scrubs.
2544For example, increasing
2545.Sy zfs_vdev_scrub_max_active
2546will cause the scrub or resilver to complete more quickly,
2547but reads and writes to have higher latency and lower throughput.
2548.Pp
2549All I/O classes have a fixed maximum number of outstanding operations,
2550except for the async write class.
2551Asynchronous writes represent the data that is committed to stable storage
2552during the syncing stage for transaction groups.
2553Transaction groups enter the syncing state periodically,
2554so the number of queued async writes will quickly burst up
2555and then bleed down to zero.
2556Rather than servicing them as quickly as possible,
2557the I/O scheduler changes the maximum number of active async write operations
2558according to the amount of dirty data in the pool.
2559Since both throughput and latency typically increase with the number of
2560concurrent operations issued to physical devices, reducing the
2561burstiness in the number of simultaneous operations also stabilizes the
2562response time of operations from other queues, in particular synchronous ones.
2563In broad strokes, the I/O scheduler will issue more concurrent operations
2564from the async write queue as there is more dirty data in the pool.
2565.
2566.Ss Async Writes
2567The number of concurrent operations issued for the async write I/O class
2568follows a piece-wise linear function defined by a few adjustable points:
2569.Bd -literal
2570       |              o---------| <-- \fBzfs_vdev_async_write_max_active\fP
2571  ^    |             /^         |
2572  |    |            / |         |
2573active |           /  |         |
2574 I/O   |          /   |         |
2575count  |         /    |         |
2576       |        /     |         |
2577       |-------o      |         | <-- \fBzfs_vdev_async_write_min_active\fP
2578      0|_______^______|_________|
2579       0%      |      |       100% of \fBzfs_dirty_data_max\fP
2580               |      |
2581               |      `-- \fBzfs_vdev_async_write_active_max_dirty_percent\fP
2582               `--------- \fBzfs_vdev_async_write_active_min_dirty_percent\fP
2583.Ed
2584.Pp
2585Until the amount of dirty data exceeds a minimum percentage of the dirty
2586data allowed in the pool, the I/O scheduler will limit the number of
2587concurrent operations to the minimum.
2588As that threshold is crossed, the number of concurrent operations issued
2589increases linearly to the maximum at the specified maximum percentage
2590of the dirty data allowed in the pool.
2591.Pp
2592Ideally, the amount of dirty data on a busy pool will stay in the sloped
2593part of the function between
2594.Sy zfs_vdev_async_write_active_min_dirty_percent
2595and
2596.Sy zfs_vdev_async_write_active_max_dirty_percent .
2597If it exceeds the maximum percentage,
2598this indicates that the rate of incoming data is
2599greater than the rate that the backend storage can handle.
2600In this case, we must further throttle incoming writes,
2601as described in the next section.
2602.
2603.Sh ZFS TRANSACTION DELAY
2604We delay transactions when we've determined that the backend storage
2605isn't able to accommodate the rate of incoming writes.
2606.Pp
2607If there is already a transaction waiting, we delay relative to when
2608that transaction will finish waiting.
2609This way the calculated delay time
2610is independent of the number of threads concurrently executing transactions.
2611.Pp
2612If we are the only waiter, wait relative to when the transaction started,
2613rather than the current time.
2614This credits the transaction for "time already served",
2615e.g. reading indirect blocks.
2616.Pp
2617The minimum time for a transaction to take is calculated as
2618.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)
2619.Pp
2620The delay has two degrees of freedom that can be adjusted via tunables.
2621The percentage of dirty data at which we start to delay is defined by
2622.Sy zfs_delay_min_dirty_percent .
2623This should typically be at or above
2624.Sy zfs_vdev_async_write_active_max_dirty_percent ,
2625so that we only start to delay after writing at full speed
2626has failed to keep up with the incoming write rate.
2627The scale of the curve is defined by
2628.Sy zfs_delay_scale .
2629Roughly speaking, this variable determines the amount of delay at the midpoint
2630of the curve.
2631.Bd -literal
2632delay
2633 10ms +-------------------------------------------------------------*+
2634      |                                                             *|
2635  9ms +                                                             *+
2636      |                                                             *|
2637  8ms +                                                             *+
2638      |                                                            * |
2639  7ms +                                                            * +
2640      |                                                            * |
2641  6ms +                                                            * +
2642      |                                                            * |
2643  5ms +                                                           *  +
2644      |                                                           *  |
2645  4ms +                                                           *  +
2646      |                                                           *  |
2647  3ms +                                                          *   +
2648      |                                                          *   |
2649  2ms +                                              (midpoint) *    +
2650      |                                                  |    **     |
2651  1ms +                                                  v ***       +
2652      |             \fBzfs_delay_scale\fP ---------->     ********         |
2653    0 +-------------------------------------*********----------------+
2654      0%                    <- \fBzfs_dirty_data_max\fP ->               100%
2655.Ed
2656.Pp
2657Note, that since the delay is added to the outstanding time remaining on the
2658most recent transaction it's effectively the inverse of IOPS.
2659Here, the midpoint of
2660.Em 500 us
2661translates to
2662.Em 2000 IOPS .
2663The shape of the curve
2664was chosen such that small changes in the amount of accumulated dirty data
2665in the first three quarters of the curve yield relatively small differences
2666in the amount of delay.
2667.Pp
2668The effects can be easier to understand when the amount of delay is
2669represented on a logarithmic scale:
2670.Bd -literal
2671delay
2672100ms +-------------------------------------------------------------++
2673      +                                                              +
2674      |                                                              |
2675      +                                                             *+
2676 10ms +                                                             *+
2677      +                                                           ** +
2678      |                                              (midpoint)  **  |
2679      +                                                  |     **    +
2680  1ms +                                                  v ****      +
2681      +             \fBzfs_delay_scale\fP ---------->        *****         +
2682      |                                             ****             |
2683      +                                          ****                +
2684100us +                                        **                    +
2685      +                                       *                      +
2686      |                                      *                       |
2687      +                                     *                        +
2688 10us +                                     *                        +
2689      +                                                              +
2690      |                                                              |
2691      +                                                              +
2692      +--------------------------------------------------------------+
2693      0%                    <- \fBzfs_dirty_data_max\fP ->               100%
2694.Ed
2695.Pp
2696Note here that only as the amount of dirty data approaches its limit does
2697the delay start to increase rapidly.
2698The goal of a properly tuned system should be to keep the amount of dirty data
2699out of that range by first ensuring that the appropriate limits are set
2700for the I/O scheduler to reach optimal throughput on the back-end storage,
2701and then by changing the value of
2702.Sy zfs_delay_scale
2703to increase the steepness of the curve.
2704