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