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