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