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