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