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