1.\" 2.\" CDDL HEADER START 3.\" 4.\" The contents of this file are subject to the terms of the 5.\" Common Development and Distribution License (the "License"). 6.\" You may not use this file except in compliance with the License. 7.\" 8.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 9.\" or http://www.opensolaris.org/os/licensing. 10.\" See the License for the specific language governing permissions 11.\" and limitations under the License. 12.\" 13.\" When distributing Covered Code, include this CDDL HEADER in each 14.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE. 15.\" If applicable, add the following below this CDDL HEADER, with the 16.\" fields enclosed by brackets "[]" replaced with your own identifying 17.\" information: Portions Copyright [yyyy] [name of copyright owner] 18.\" 19.\" CDDL HEADER END 20.\" 21.\" Copyright (c) 2009 Sun Microsystems, Inc. All Rights Reserved. 22.\" Copyright 2011 Joshua M. Clulow <josh@sysmgr.org> 23.\" Copyright (c) 2011, 2019 by Delphix. All rights reserved. 24.\" Copyright (c) 2011, Pawel Jakub Dawidek <pjd@FreeBSD.org> 25.\" Copyright (c) 2012, Glen Barber <gjb@FreeBSD.org> 26.\" Copyright (c) 2012, Bryan Drewery <bdrewery@FreeBSD.org> 27.\" Copyright (c) 2013, Steven Hartland <smh@FreeBSD.org> 28.\" Copyright (c) 2013 by Saso Kiselkov. All rights reserved. 29.\" Copyright (c) 2014, Joyent, Inc. All rights reserved. 30.\" Copyright (c) 2014 by Adam Stevko. All rights reserved. 31.\" Copyright (c) 2014 Integros [integros.com] 32.\" Copyright (c) 2016 Nexenta Systems, Inc. All Rights Reserved. 33.\" Copyright (c) 2014, Xin LI <delphij@FreeBSD.org> 34.\" Copyright (c) 2014-2015, The FreeBSD Foundation, All Rights Reserved. 35.\" Copyright 2019 Richard Laager. All rights reserved. 36.\" Copyright 2018 Nexenta Systems, Inc. 37.\" Copyright 2019 Joyent, Inc. 38.\" Copyright (c) 2019, Kjeld Schouten-Lebbing 39.\" 40.Dd May 24, 2021 41.Dt ZFSPROPS 7 42.Os 43. 44.Sh NAME 45.Nm zfsprops 46.Nd native and user-defined properties of ZFS datasets 47. 48.Sh DESCRIPTION 49Properties are divided into two types, native properties and user-defined 50.Po or 51.Qq user 52.Pc 53properties. 54Native properties either export internal statistics or control ZFS behavior. 55In addition, native properties are either editable or read-only. 56User properties have no effect on ZFS behavior, but you can use them to annotate 57datasets in a way that is meaningful in your environment. 58For more information about user properties, see the 59.Sx User Properties 60section, below. 61. 62.Ss Native Properties 63Every dataset has a set of properties that export statistics about the dataset 64as well as control various behaviors. 65Properties are inherited from the parent unless overridden by the child. 66Some properties apply only to certain types of datasets 67.Pq file systems, volumes, or snapshots . 68.Pp 69The values of numeric properties can be specified using human-readable suffixes 70.Po for example, 71.Sy k , 72.Sy KB , 73.Sy M , 74.Sy Gb , 75and so forth, up to 76.Sy Z 77for zettabyte 78.Pc . 79The following are all valid 80.Pq and equal 81specifications: 82.Li 1536M, 1.5g, 1.50GB . 83.Pp 84The values of non-numeric properties are case sensitive and must be lowercase, 85except for 86.Sy mountpoint , 87.Sy sharenfs , 88and 89.Sy sharesmb . 90.Pp 91The following native properties consist of read-only statistics about the 92dataset. 93These properties can be neither set, nor inherited. 94Native properties apply to all dataset types unless otherwise noted. 95.Bl -tag -width "usedbyrefreservation" 96.It Sy available 97The amount of space available to the dataset and all its children, assuming that 98there is no other activity in the pool. 99Because space is shared within a pool, availability can be limited by any number 100of factors, including physical pool size, quotas, reservations, or other 101datasets within the pool. 102.Pp 103This property can also be referred to by its shortened column name, 104.Sy avail . 105.It Sy compressratio 106For non-snapshots, the compression ratio achieved for the 107.Sy used 108space of this dataset, expressed as a multiplier. 109The 110.Sy used 111property includes descendant datasets, and, for clones, does not include the 112space shared with the origin snapshot. 113For snapshots, the 114.Sy compressratio 115is the same as the 116.Sy refcompressratio 117property. 118Compression can be turned on by running: 119.Nm zfs Cm set Sy compression Ns = Ns Sy on Ar dataset . 120The default value is 121.Sy off . 122.It Sy createtxg 123The transaction group (txg) in which the dataset was created. 124Bookmarks have the same 125.Sy createtxg 126as the snapshot they are initially tied to. 127This property is suitable for ordering a list of snapshots, 128e.g. for incremental send and receive. 129.It Sy creation 130The time this dataset was created. 131.It Sy clones 132For snapshots, this property is a comma-separated list of filesystems or volumes 133which are clones of this snapshot. 134The clones' 135.Sy origin 136property is this snapshot. 137If the 138.Sy clones 139property is not empty, then this snapshot can not be destroyed 140.Po even with the 141.Fl r 142or 143.Fl f 144options 145.Pc . 146The roles of origin and clone can be swapped by promoting the clone with the 147.Nm zfs Cm promote 148command. 149.It Sy defer_destroy 150This property is 151.Sy on 152if the snapshot has been marked for deferred destroy by using the 153.Nm zfs Cm destroy Fl d 154command. 155Otherwise, the property is 156.Sy off . 157.It Sy encryptionroot 158For encrypted datasets, indicates where the dataset is currently inheriting its 159encryption key from. 160Loading or unloading a key for the 161.Sy encryptionroot 162will implicitly load / unload the key for any inheriting datasets (see 163.Nm zfs Cm load-key 164and 165.Nm zfs Cm unload-key 166for details). 167Clones will always share an 168encryption key with their origin. 169See the 170.Sx Encryption 171section of 172.Xr zfs-load-key 8 173for details. 174.It Sy filesystem_count 175The total number of filesystems and volumes that exist under this location in 176the dataset tree. 177This value is only available when a 178.Sy filesystem_limit 179has been set somewhere in the tree under which the dataset resides. 180.It Sy keystatus 181Indicates if an encryption key is currently loaded into ZFS. 182The possible values are 183.Sy none , 184.Sy available , 185and 186.Sy unavailable . 187See 188.Nm zfs Cm load-key 189and 190.Nm zfs Cm unload-key . 191.It Sy guid 192The 64 bit GUID of this dataset or bookmark which does not change over its 193entire lifetime. 194When a snapshot is sent to another pool, the received snapshot has the same GUID. 195Thus, the 196.Sy guid 197is suitable to identify a snapshot across pools. 198.It Sy logicalreferenced 199The amount of space that is 200.Qq logically 201accessible by this dataset. 202See the 203.Sy referenced 204property. 205The logical space ignores the effect of the 206.Sy compression 207and 208.Sy copies 209properties, giving a quantity closer to the amount of data that applications 210see. 211However, it does include space consumed by metadata. 212.Pp 213This property can also be referred to by its shortened column name, 214.Sy lrefer . 215.It Sy logicalused 216The amount of space that is 217.Qq logically 218consumed by this dataset and all its descendents. 219See the 220.Sy used 221property. 222The logical space ignores the effect of the 223.Sy compression 224and 225.Sy copies 226properties, giving a quantity closer to the amount of data that applications 227see. 228However, it does include space consumed by metadata. 229.Pp 230This property can also be referred to by its shortened column name, 231.Sy lused . 232.It Sy mounted 233For file systems, indicates whether the file system is currently mounted. 234This property can be either 235.Sy yes 236or 237.Sy no . 238.It Sy objsetid 239A unique identifier for this dataset within the pool. 240Unlike the dataset's 241.Sy guid , No the Sy objsetid 242of a dataset is not transferred to other pools when the snapshot is copied 243with a send/receive operation. 244The 245.Sy objsetid 246can be reused (for a new dataset) after the dataset is deleted. 247.It Sy origin 248For cloned file systems or volumes, the snapshot from which the clone was 249created. 250See also the 251.Sy clones 252property. 253.It Sy receive_resume_token 254For filesystems or volumes which have saved partially-completed state from 255.Nm zfs Cm receive Fl s , 256this opaque token can be provided to 257.Nm zfs Cm send Fl t 258to resume and complete the 259.Nm zfs Cm receive . 260.It Sy redact_snaps 261For bookmarks, this is the list of snapshot guids the bookmark contains a redaction 262list for. 263For snapshots, this is the list of snapshot guids the snapshot is redacted with 264respect to. 265.It Sy referenced 266The amount of data that is accessible by this dataset, which may or may not be 267shared with other datasets in the pool. 268When a snapshot or clone is created, it initially references the same amount of 269space as the file system or snapshot it was created from, since its contents are 270identical. 271.Pp 272This property can also be referred to by its shortened column name, 273.Sy refer . 274.It Sy refcompressratio 275The compression ratio achieved for the 276.Sy referenced 277space of this dataset, expressed as a multiplier. 278See also the 279.Sy compressratio 280property. 281.It Sy snapshot_count 282The total number of snapshots that exist under this location in the dataset 283tree. 284This value is only available when a 285.Sy snapshot_limit 286has been set somewhere in the tree under which the dataset resides. 287.It Sy type 288The type of dataset: 289.Sy filesystem , 290.Sy volume , 291.Sy snapshot , 292or 293.Sy bookmark . 294.It Sy used 295The amount of space consumed by this dataset and all its descendents. 296This is the value that is checked against this dataset's quota and reservation. 297The space used does not include this dataset's reservation, but does take into 298account the reservations of any descendent datasets. 299The amount of space that a dataset consumes from its parent, as well as the 300amount of space that is freed if this dataset is recursively destroyed, is the 301greater of its space used and its reservation. 302.Pp 303The used space of a snapshot 304.Po see the 305.Sx Snapshots 306section of 307.Xr zfsconcepts 7 308.Pc 309is space that is referenced exclusively by this snapshot. 310If this snapshot is destroyed, the amount of 311.Sy used 312space will be freed. 313Space that is shared by multiple snapshots isn't accounted for in this metric. 314When a snapshot is destroyed, space that was previously shared with this 315snapshot can become unique to snapshots adjacent to it, thus changing the used 316space of those snapshots. 317The used space of the latest snapshot can also be affected by changes in the 318file system. 319Note that the 320.Sy used 321space of a snapshot is a subset of the 322.Sy written 323space of the snapshot. 324.Pp 325The amount of space used, available, or referenced does not take into account 326pending changes. 327Pending changes are generally accounted for within a few seconds. 328Committing a change to a disk using 329.Xr fsync 2 330or 331.Sy O_SYNC 332does not necessarily guarantee that the space usage information is updated 333immediately. 334.It Sy usedby* 335The 336.Sy usedby* 337properties decompose the 338.Sy used 339properties into the various reasons that space is used. 340Specifically, 341.Sy used No = 342.Sy usedbychildren No + 343.Sy usedbydataset No + 344.Sy usedbyrefreservation No + 345.Sy usedbysnapshots . 346These properties are only available for datasets created on 347.Nm zpool 348.Qo version 13 Qc 349pools. 350.It Sy usedbychildren 351The amount of space used by children of this dataset, which would be freed if 352all the dataset's children were destroyed. 353.It Sy usedbydataset 354The amount of space used by this dataset itself, which would be freed if the 355dataset were destroyed 356.Po after first removing any 357.Sy refreservation 358and destroying any necessary snapshots or descendents 359.Pc . 360.It Sy usedbyrefreservation 361The amount of space used by a 362.Sy refreservation 363set on this dataset, which would be freed if the 364.Sy refreservation 365was removed. 366.It Sy usedbysnapshots 367The amount of space consumed by snapshots of this dataset. 368In particular, it is the amount of space that would be freed if all of this 369dataset's snapshots were destroyed. 370Note that this is not simply the sum of the snapshots' 371.Sy used 372properties because space can be shared by multiple snapshots. 373.It Sy userused Ns @ Ns Ar user 374The amount of space consumed by the specified user in this dataset. 375Space is charged to the owner of each file, as displayed by 376.Nm ls Fl l . 377The amount of space charged is displayed by 378.Nm du No and Nm ls Fl s . 379See the 380.Nm zfs Cm userspace 381command for more information. 382.Pp 383Unprivileged users can access only their own space usage. 384The root user, or a user who has been granted the 385.Sy userused 386privilege with 387.Nm zfs Cm allow , 388can access everyone's usage. 389.Pp 390The 391.Sy userused Ns @ Ns Ar … 392properties are not displayed by 393.Nm zfs Cm get Sy all . 394The user's name must be appended after the 395.Sy @ 396symbol, using one of the following forms: 397.Bl -bullet -compact -offset 4n 398.It 399POSIX name 400.Pq Qq joe 401.It 402POSIX numeric ID 403.Pq Qq 789 404.It 405SID name 406.Pq Qq joe.smith@mydomain 407.It 408SID numeric ID 409.Pq Qq S-1-123-456-789 410.El 411.Pp 412Files created on Linux always have POSIX owners. 413.It Sy userobjused Ns @ Ns Ar user 414The 415.Sy userobjused 416property is similar to 417.Sy userused 418but instead it counts the number of objects consumed by a user. 419This property counts all objects allocated on behalf of the user, 420it may differ from the results of system tools such as 421.Nm df Fl i . 422.Pp 423When the property 424.Sy xattr Ns = Ns Sy on 425is set on a file system additional objects will be created per-file to store 426extended attributes. 427These additional objects are reflected in the 428.Sy userobjused 429value and are counted against the user's 430.Sy userobjquota . 431When a file system is configured to use 432.Sy xattr Ns = Ns Sy sa 433no additional internal objects are normally required. 434.It Sy userrefs 435This property is set to the number of user holds on this snapshot. 436User holds are set by using the 437.Nm zfs Cm hold 438command. 439.It Sy groupused Ns @ Ns Ar group 440The amount of space consumed by the specified group in this dataset. 441Space is charged to the group of each file, as displayed by 442.Nm ls Fl l . 443See the 444.Sy userused Ns @ Ns Ar user 445property for more information. 446.Pp 447Unprivileged users can only access their own groups' space usage. 448The root user, or a user who has been granted the 449.Sy groupused 450privilege with 451.Nm zfs Cm allow , 452can access all groups' usage. 453.It Sy groupobjused Ns @ Ns Ar group 454The number of objects consumed by the specified group in this dataset. 455Multiple objects may be charged to the group for each file when extended 456attributes are in use. 457See the 458.Sy userobjused Ns @ Ns Ar user 459property for more information. 460.Pp 461Unprivileged users can only access their own groups' space usage. 462The root user, or a user who has been granted the 463.Sy groupobjused 464privilege with 465.Nm zfs Cm allow , 466can access all groups' usage. 467.It Sy projectused Ns @ Ns Ar project 468The amount of space consumed by the specified project in this dataset. 469Project is identified via the project identifier (ID) that is object-based 470numeral attribute. 471An object can inherit the project ID from its parent object (if the 472parent has the flag of inherit project ID that can be set and changed via 473.Nm chattr Fl /+P 474or 475.Nm zfs project Fl s ) 476when being created. 477The privileged user can set and change object's project 478ID via 479.Nm chattr Fl p 480or 481.Nm zfs project Fl s 482anytime. 483Space is charged to the project of each file, as displayed by 484.Nm lsattr Fl p 485or 486.Nm zfs project . 487See the 488.Sy userused Ns @ Ns Ar user 489property for more information. 490.Pp 491The root user, or a user who has been granted the 492.Sy projectused 493privilege with 494.Nm zfs allow , 495can access all projects' usage. 496.It Sy projectobjused Ns @ Ns Ar project 497The 498.Sy projectobjused 499is similar to 500.Sy projectused 501but instead it counts the number of objects consumed by project. 502When the property 503.Sy xattr Ns = Ns Sy on 504is set on a fileset, ZFS will create additional objects per-file to store 505extended attributes. 506These additional objects are reflected in the 507.Sy projectobjused 508value and are counted against the project's 509.Sy projectobjquota . 510When a filesystem is configured to use 511.Sy xattr Ns = Ns Sy sa 512no additional internal objects are required. 513See the 514.Sy userobjused Ns @ Ns Ar user 515property for more information. 516.Pp 517The root user, or a user who has been granted the 518.Sy projectobjused 519privilege with 520.Nm zfs allow , 521can access all projects' objects usage. 522.It Sy volblocksize 523For volumes, specifies the block size of the volume. 524The 525.Sy blocksize 526cannot be changed once the volume has been written, so it should be set at 527volume creation time. 528The default 529.Sy blocksize 530for volumes is 16 Kbytes. 531Any power of 2 from 512 bytes to 128 Kbytes is valid. 532.Pp 533This property can also be referred to by its shortened column name, 534.Sy volblock . 535.It Sy written 536The amount of space 537.Sy referenced 538by this dataset, that was written since the previous snapshot 539.Pq i.e. that is not referenced by the previous snapshot . 540.It Sy written Ns @ Ns Ar snapshot 541The amount of 542.Sy referenced 543space written to this dataset since the specified snapshot. 544This is the space that is referenced by this dataset but was not referenced by 545the specified snapshot. 546.Pp 547The 548.Ar snapshot 549may be specified as a short snapshot name 550.Pq just the part after the Sy @ , 551in which case it will be interpreted as a snapshot in the same filesystem as 552this dataset. 553The 554.Ar snapshot 555may be a full snapshot name 556.Pq Ar filesystem Ns @ Ns Ar snapshot , 557which for clones may be a snapshot in the origin's filesystem 558.Pq or the origin of the origin's filesystem, etc. 559.El 560.Pp 561The following native properties can be used to change the behavior of a ZFS 562dataset. 563.Bl -tag -width "" 564.It Xo 565.Sy aclinherit Ns = Ns Sy discard Ns | Ns Sy noallow Ns | Ns 566.Sy restricted Ns | Ns Sy passthrough Ns | Ns Sy passthrough-x 567.Xc 568Controls how ACEs are inherited when files and directories are created. 569.Bl -tag -compact -offset 4n -width "passthrough-x" 570.It Sy discard 571does not inherit any ACEs. 572.It Sy noallow 573only inherits inheritable ACEs that specify 574.Qq deny 575permissions. 576.It Sy restricted 577default, removes the 578.Sy write_acl 579and 580.Sy write_owner 581permissions when the ACE is inherited. 582.It Sy passthrough 583inherits all inheritable ACEs without any modifications. 584.It Sy passthrough-x 585same meaning as 586.Sy passthrough , 587except that the 588.Sy owner@ , group@ , No and Sy everyone@ 589ACEs inherit the execute permission only if the file creation mode also requests 590the execute bit. 591.El 592.Pp 593When the property value is set to 594.Sy passthrough , 595files are created with a mode determined by the inheritable ACEs. 596If no inheritable ACEs exist that affect the mode, then the mode is set in 597accordance to the requested mode from the application. 598.Pp 599The 600.Sy aclinherit 601property does not apply to POSIX ACLs. 602.It Xo 603.Sy aclmode Ns = Ns Sy discard Ns | Ns Sy groupmask Ns | Ns 604.Sy passthrough Ns | Ns Sy restricted Ns 605.Xc 606Controls how an ACL is modified during chmod(2) and how inherited ACEs 607are modified by the file creation mode: 608.Bl -tag -compact -offset 4n -width "passthrough" 609.It Sy discard 610default, deletes all 611.Sy ACEs 612except for those representing 613the mode of the file or directory requested by 614.Xr chmod 2 . 615.It Sy groupmask 616reduces permissions granted in all 617.Sy ALLOW 618entries found in the 619.Sy ACL 620such that they are no greater than the group permissions specified by 621.Xr chmod 2 . 622.It Sy passthrough 623indicates that no changes are made to the ACL other than creating or updating 624the necessary ACL entries to represent the new mode of the file or directory. 625.It Sy restricted 626will cause the 627.Xr chmod 2 628operation to return an error when used on any file or directory which has 629a non-trivial ACL whose entries can not be represented by a mode. 630.Xr chmod 2 631is required to change the set user ID, set group ID, or sticky bits on a file 632or directory, as they do not have equivalent ACL entries. 633In order to use 634.Xr chmod 2 635on a file or directory with a non-trivial ACL when 636.Sy aclmode 637is set to 638.Sy restricted , 639you must first remove all ACL entries which do not represent the current mode. 640.El 641.It Sy acltype Ns = Ns Sy off Ns | Ns Sy nfsv4 Ns | Ns Sy posix 642Controls whether ACLs are enabled and if so what type of ACL to use. 643When this property is set to a type of ACL not supported by the current 644platform, the behavior is the same as if it were set to 645.Sy off . 646.Bl -tag -compact -offset 4n -width "posixacl" 647.It Sy off 648default on Linux, when a file system has the 649.Sy acltype 650property set to off then ACLs are disabled. 651.It Sy noacl 652an alias for 653.Sy off 654.It Sy nfsv4 655default on 656.Fx , 657indicates that NFSv4-style ZFS ACLs should be used. 658These ACLs can be managed with the 659.Xr getfacl 1 660and 661.Xr setfacl 1 . 662The 663.Sy nfsv4 664ZFS ACL type is not yet supported on Linux. 665.It Sy posix 666indicates POSIX ACLs should be used. 667POSIX ACLs are specific to Linux and are not functional on other platforms. 668POSIX ACLs are stored as an extended 669attribute and therefore will not overwrite any existing NFSv4 ACLs which 670may be set. 671.It Sy posixacl 672an alias for 673.Sy posix 674.El 675.Pp 676To obtain the best performance when setting 677.Sy posix 678users are strongly encouraged to set the 679.Sy xattr Ns = Ns Sy sa 680property. 681This will result in the POSIX ACL being stored more efficiently on disk. 682But as a consequence, all new extended attributes will only be 683accessible from OpenZFS implementations which support the 684.Sy xattr Ns = Ns Sy sa 685property. 686See the 687.Sy xattr 688property for more details. 689.It Sy atime Ns = Ns Sy on Ns | Ns Sy off 690Controls whether the access time for files is updated when they are read. 691Turning this property off avoids producing write traffic when reading files and 692can result in significant performance gains, though it might confuse mailers 693and other similar utilities. 694The values 695.Sy on 696and 697.Sy off 698are equivalent to the 699.Sy atime 700and 701.Sy noatime 702mount options. 703The default value is 704.Sy on . 705See also 706.Sy relatime 707below. 708.It Sy canmount Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Sy noauto 709If this property is set to 710.Sy off , 711the file system cannot be mounted, and is ignored by 712.Nm zfs Cm mount Fl a . 713Setting this property to 714.Sy off 715is similar to setting the 716.Sy mountpoint 717property to 718.Sy none , 719except that the dataset still has a normal 720.Sy mountpoint 721property, which can be inherited. 722Setting this property to 723.Sy off 724allows datasets to be used solely as a mechanism to inherit properties. 725One example of setting 726.Sy canmount Ns = Ns Sy off 727is to have two datasets with the same 728.Sy mountpoint , 729so that the children of both datasets appear in the same directory, but might 730have different inherited characteristics. 731.Pp 732When set to 733.Sy noauto , 734a dataset can only be mounted and unmounted explicitly. 735The dataset is not mounted automatically when the dataset is created or 736imported, nor is it mounted by the 737.Nm zfs Cm mount Fl a 738command or unmounted by the 739.Nm zfs Cm unmount Fl a 740command. 741.Pp 742This property is not inherited. 743.It Xo 744.Sy checksum Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Sy fletcher2 Ns | Ns 745.Sy fletcher4 Ns | Ns Sy sha256 Ns | Ns Sy noparity Ns | Ns 746.Sy sha512 Ns | Ns Sy skein Ns | Ns Sy edonr 747.Xc 748Controls the checksum used to verify data integrity. 749The default value is 750.Sy on , 751which automatically selects an appropriate algorithm 752.Po currently, 753.Sy fletcher4 , 754but this may change in future releases 755.Pc . 756The value 757.Sy off 758disables integrity checking on user data. 759The value 760.Sy noparity 761not only disables integrity but also disables maintaining parity for user data. 762This setting is used internally by a dump device residing on a RAID-Z pool and 763should not be used by any other dataset. 764Disabling checksums is 765.Em NOT 766a recommended practice. 767.Pp 768The 769.Sy sha512 , 770.Sy skein , 771and 772.Sy edonr 773checksum algorithms require enabling the appropriate features on the pool. 774.Pp 775Please see 776.Xr zpool-features 7 777for more information on these algorithms. 778.Pp 779Changing this property affects only newly-written data. 780.It Xo 781.Sy compression Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Sy gzip Ns | Ns 782.Sy gzip- Ns Ar N Ns | Ns Sy lz4 Ns | Ns Sy lzjb Ns | Ns Sy zle Ns | Ns Sy zstd Ns | Ns 783.Sy zstd- Ns Ar N Ns | Ns Sy zstd-fast Ns | Ns Sy zstd-fast- Ns Ar N 784.Xc 785Controls the compression algorithm used for this dataset. 786.Pp 787When set to 788.Sy on 789(the default), indicates that the current default compression algorithm should be used. 790The default balances compression and decompression speed, with compression ratio 791and is expected to work well on a wide variety of workloads. 792Unlike all other settings for this property, 793.Sy on 794does not select a fixed compression type. 795As new compression algorithms are added to ZFS and enabled on a pool, the 796default compression algorithm may change. 797The current default compression algorithm is either 798.Sy lzjb 799or, if the 800.Sy lz4_compress 801feature is enabled, 802.Sy lz4 . 803.Pp 804The 805.Sy lz4 806compression algorithm is a high-performance replacement for the 807.Sy lzjb 808algorithm. 809It features significantly faster compression and decompression, as well as a 810moderately higher compression ratio than 811.Sy lzjb , 812but can only be used on pools with the 813.Sy lz4_compress 814feature set to 815.Sy enabled . 816See 817.Xr zpool-features 7 818for details on ZFS feature flags and the 819.Sy lz4_compress 820feature. 821.Pp 822The 823.Sy lzjb 824compression algorithm is optimized for performance while providing decent data 825compression. 826.Pp 827The 828.Sy gzip 829compression algorithm uses the same compression as the 830.Xr gzip 1 831command. 832You can specify the 833.Sy gzip 834level by using the value 835.Sy gzip- Ns Ar N , 836where 837.Ar N 838is an integer from 1 839.Pq fastest 840to 9 841.Pq best compression ratio . 842Currently, 843.Sy gzip 844is equivalent to 845.Sy gzip-6 846.Po which is also the default for 847.Xr gzip 1 848.Pc . 849.Pp 850The 851.Sy zstd 852compression algorithm provides both high compression ratios and good performance. 853You can specify the 854.Sy zstd 855level by using the value 856.Sy zstd- Ns Ar N , 857where 858.Ar N 859is an integer from 1 860.Pq fastest 861to 19 862.Pq best compression ratio . 863.Sy zstd 864is equivalent to 865.Sy zstd-3 . 866.Pp 867Faster speeds at the cost of the compression ratio can be requested by 868setting a negative 869.Sy zstd 870level. 871This is done using 872.Sy zstd-fast- Ns Ar N , 873where 874.Ar N 875is an integer in 876.Bq Sy 1 Ns - Ns Sy 10 , 20 , 30 , No … , Sy 100 , 500 , 1000 877which maps to a negative 878.Sy zstd 879level. 880The lower the level the faster the compression \(em 881.Sy 1000 882provides the fastest compression and lowest compression ratio. 883.Sy zstd-fast 884is equivalent to 885.Sy zstd-fast- Ns Ar 1 . 886.Pp 887The 888.Sy zle 889compression algorithm compresses runs of zeros. 890.Pp 891This property can also be referred to by its shortened column name 892.Sy compress . 893Changing this property affects only newly-written data. 894.Pp 895When any setting except 896.Sy off 897is selected, compression will explicitly check for blocks consisting of only 898zeroes (the NUL byte). 899When a zero-filled block is detected, it is stored as 900a hole and not compressed using the indicated compression algorithm. 901.Pp 902Any block being compressed must be no larger than 7/8 of its original size 903after compression, otherwise the compression will not be considered worthwhile 904and the block saved uncompressed. 905Note that when the logical block is less than 9068 times the disk sector size this effectively reduces the necessary compression 907ratio; for example, 8 KiB blocks on disks with 4 KiB disk sectors must compress to 1/2 908or less of their original size. 909.It Xo 910.Sy context Ns = Ns Sy none Ns | Ns 911.Ar SELinux-User : Ns Ar SELinux-Role : Ns Ar SELinux-Type : Ns Ar Sensitivity-Level 912.Xc 913This flag sets the SELinux context for all files in the file system under 914a mount point for that file system. 915See 916.Xr selinux 8 917for more information. 918.It Xo 919.Sy fscontext Ns = Ns Sy none Ns | Ns 920.Ar SELinux-User : Ns Ar SELinux-Role : Ns Ar SELinux-Type : Ns Ar Sensitivity-Level 921.Xc 922This flag sets the SELinux context for the file system file system being 923mounted. 924See 925.Xr selinux 8 926for more information. 927.It Xo 928.Sy defcontext Ns = Ns Sy none Ns | Ns 929.Ar SELinux-User : Ns Ar SELinux-Role : Ns Ar SELinux-Type : Ns Ar Sensitivity-Level 930.Xc 931This flag sets the SELinux default context for unlabeled files. 932See 933.Xr selinux 8 934for more information. 935.It Xo 936.Sy rootcontext Ns = Ns Sy none Ns | Ns 937.Ar SELinux-User : Ns Ar SELinux-Role : Ns Ar SELinux-Type : Ns Ar Sensitivity-Level 938.Xc 939This flag sets the SELinux context for the root inode of the file system. 940See 941.Xr selinux 8 942for more information. 943.It Sy copies Ns = Ns Sy 1 Ns | Ns Sy 2 Ns | Ns Sy 3 944Controls the number of copies of data stored for this dataset. 945These copies are in addition to any redundancy provided by the pool, for 946example, mirroring or RAID-Z. 947The copies are stored on different disks, if possible. 948The space used by multiple copies is charged to the associated file and dataset, 949changing the 950.Sy used 951property and counting against quotas and reservations. 952.Pp 953Changing this property only affects newly-written data. 954Therefore, set this property at file system creation time by using the 955.Fl o Sy copies Ns = Ns Ar N 956option. 957.Pp 958Remember that ZFS will not import a pool with a missing top-level vdev. 959Do 960.Em NOT 961create, for example a two-disk striped pool and set 962.Sy copies Ns = Ns Ar 2 963on some datasets thinking you have setup redundancy for them. 964When a disk fails you will not be able to import the pool 965and will have lost all of your data. 966.Pp 967Encrypted datasets may not have 968.Sy copies Ns = Ns Ar 3 969since the implementation stores some encryption metadata where the third copy 970would normally be. 971.It Sy devices Ns = Ns Sy on Ns | Ns Sy off 972Controls whether device nodes can be opened on this file system. 973The default value is 974.Sy on . 975The values 976.Sy on 977and 978.Sy off 979are equivalent to the 980.Sy dev 981and 982.Sy nodev 983mount options. 984.It Xo 985.Sy dedup Ns = Ns Sy off Ns | Ns Sy on Ns | Ns Sy verify Ns | Ns 986.Sy sha256 Ns Oo , Ns Sy verify Oc Ns | Ns Sy sha512 Ns Oo , Ns Sy verify Oc Ns | Ns Sy skein Ns Oo , Ns Sy verify Oc Ns | Ns 987.Sy edonr , Ns Sy verify 988.Xc 989Configures deduplication for a dataset. 990The default value is 991.Sy off . 992The default deduplication checksum is 993.Sy sha256 994(this may change in the future). 995When 996.Sy dedup 997is enabled, the checksum defined here overrides the 998.Sy checksum 999property. 1000Setting the value to 1001.Sy verify 1002has the same effect as the setting 1003.Sy sha256 , Ns Sy verify . 1004.Pp 1005If set to 1006.Sy verify , 1007ZFS will do a byte-to-byte comparison in case of two blocks having the same 1008signature to make sure the block contents are identical. 1009Specifying 1010.Sy verify 1011is mandatory for the 1012.Sy edonr 1013algorithm. 1014.Pp 1015Unless necessary, deduplication should 1016.Em not 1017be enabled on a system. 1018See the 1019.Sx Deduplication 1020section of 1021.Xr zfsconcepts 7 . 1022.It Xo 1023.Sy dnodesize Ns = Ns Sy legacy Ns | Ns Sy auto Ns | Ns Sy 1k Ns | Ns 1024.Sy 2k Ns | Ns Sy 4k Ns | Ns Sy 8k Ns | Ns Sy 16k 1025.Xc 1026Specifies a compatibility mode or literal value for the size of dnodes in the 1027file system. 1028The default value is 1029.Sy legacy . 1030Setting this property to a value other than 1031.Sy legacy No requires the Sy large_dnode No pool feature to be enabled. 1032.Pp 1033Consider setting 1034.Sy dnodesize 1035to 1036.Sy auto 1037if the dataset uses the 1038.Sy xattr Ns = Ns Sy sa 1039property setting and the workload makes heavy use of extended attributes. 1040This 1041may be applicable to SELinux-enabled systems, Lustre servers, and Samba 1042servers, for example. 1043Literal values are supported for cases where the optimal 1044size is known in advance and for performance testing. 1045.Pp 1046Leave 1047.Sy dnodesize 1048set to 1049.Sy legacy 1050if you need to receive a send stream of this dataset on a pool that doesn't 1051enable the 1052.Sy large_dnode 1053feature, or if you need to import this pool on a system that doesn't support the 1054.Sy large_dnode No feature. 1055.Pp 1056This property can also be referred to by its shortened column name, 1057.Sy dnsize . 1058.It Xo 1059.Sy encryption Ns = Ns Sy off Ns | Ns Sy on Ns | Ns Sy aes-128-ccm Ns | Ns 1060.Sy aes-192-ccm Ns | Ns Sy aes-256-ccm Ns | Ns Sy aes-128-gcm Ns | Ns 1061.Sy aes-192-gcm Ns | Ns Sy aes-256-gcm 1062.Xc 1063Controls the encryption cipher suite (block cipher, key length, and mode) used 1064for this dataset. 1065Requires the 1066.Sy encryption 1067feature to be enabled on the pool. 1068Requires a 1069.Sy keyformat 1070to be set at dataset creation time. 1071.Pp 1072Selecting 1073.Sy encryption Ns = Ns Sy on 1074when creating a dataset indicates that the default encryption suite will be 1075selected, which is currently 1076.Sy aes-256-gcm . 1077In order to provide consistent data protection, encryption must be specified at 1078dataset creation time and it cannot be changed afterwards. 1079.Pp 1080For more details and caveats about encryption see the 1081.Sx Encryption 1082section of 1083.Xr zfs-load-key 8 . 1084.It Sy keyformat Ns = Ns Sy raw Ns | Ns Sy hex Ns | Ns Sy passphrase 1085Controls what format the user's encryption key will be provided as. 1086This property is only set when the dataset is encrypted. 1087.Pp 1088Raw keys and hex keys must be 32 bytes long (regardless of the chosen 1089encryption suite) and must be randomly generated. 1090A raw key can be generated with the following command: 1091.Dl # Nm dd Sy if=/dev/urandom bs=32 count=1 Sy of= Ns Pa /path/to/output/key 1092.Pp 1093Passphrases must be between 8 and 512 bytes long and will be processed through 1094PBKDF2 before being used (see the 1095.Sy pbkdf2iters 1096property). 1097Even though the encryption suite cannot be changed after dataset creation, 1098the keyformat can be with 1099.Nm zfs Cm change-key . 1100.It Xo 1101.Sy keylocation Ns = Ns Sy prompt Ns | Ns Sy file:// Ns Ar /absolute/file/path Ns | Ns Sy https:// Ns Ar address Ns | Ns Sy http:// Ns Ar address 1102.Xc 1103Controls where the user's encryption key will be loaded from by default for 1104commands such as 1105.Nm zfs Cm load-key 1106and 1107.Nm zfs Cm mount Fl l . 1108This property is only set for encrypted datasets which are encryption roots. 1109If unspecified, the default is 1110.Sy prompt . 1111.Pp 1112Even though the encryption suite cannot be changed after dataset creation, the 1113keylocation can be with either 1114.Nm zfs Cm set 1115or 1116.Nm zfs Cm change-key . 1117If 1118.Sy prompt 1119is selected ZFS will ask for the key at the command prompt when it is required 1120to access the encrypted data (see 1121.Nm zfs Cm load-key 1122for details). 1123This setting will also allow the key to be passed in via the standard input stream, 1124but users should be careful not to place keys which should be kept secret on 1125the command line. 1126If a file URI is selected, the key will be loaded from the 1127specified absolute file path. 1128If an HTTPS or HTTP URL is selected, it will be GETted using 1129.Xr fetch 3 , 1130libcurl, or nothing, depending on compile-time configuration and run-time availability. 1131The 1132.Sy SSL_CA_CERT_FILE 1133environment variable can be set to set the location 1134of the concatenated certificate store. 1135The 1136.Sy SSL_CA_CERT_PATH 1137environment variable can be set to override the location 1138of the directory containing the certificate authority bundle. 1139The 1140.Sy SSL_CLIENT_CERT_FILE 1141and 1142.Sy SSL_CLIENT_KEY_FILE 1143environment variables can be set to configure the path 1144to the client certificate and its key. 1145.It Sy pbkdf2iters Ns = Ns Ar iterations 1146Controls the number of PBKDF2 iterations that a 1147.Sy passphrase 1148encryption key should be run through when processing it into an encryption key. 1149This property is only defined when encryption is enabled and a keyformat of 1150.Sy passphrase 1151is selected. 1152The goal of PBKDF2 is to significantly increase the 1153computational difficulty needed to brute force a user's passphrase. 1154This is accomplished by forcing the attacker to run each passphrase through a 1155computationally expensive hashing function many times before they arrive at the 1156resulting key. 1157A user who actually knows the passphrase will only have to pay this cost once. 1158As CPUs become better at processing, this number should be 1159raised to ensure that a brute force attack is still not possible. 1160The current default is 1161.Sy 350000 1162and the minimum is 1163.Sy 100000 . 1164This property may be changed with 1165.Nm zfs Cm change-key . 1166.It Sy exec Ns = Ns Sy on Ns | Ns Sy off 1167Controls whether processes can be executed from within this file system. 1168The default value is 1169.Sy on . 1170The values 1171.Sy on 1172and 1173.Sy off 1174are equivalent to the 1175.Sy exec 1176and 1177.Sy noexec 1178mount options. 1179.It Sy filesystem_limit Ns = Ns Ar count Ns | Ns Sy none 1180Limits the number of filesystems and volumes that can exist under this point in 1181the dataset tree. 1182The limit is not enforced if the user is allowed to change the limit. 1183Setting a 1184.Sy filesystem_limit 1185to 1186.Sy on 1187a descendent of a filesystem that already has a 1188.Sy filesystem_limit 1189does not override the ancestor's 1190.Sy filesystem_limit , 1191but rather imposes an additional limit. 1192This feature must be enabled to be used 1193.Po see 1194.Xr zpool-features 7 1195.Pc . 1196.It Sy special_small_blocks Ns = Ns Ar size 1197This value represents the threshold block size for including small file 1198blocks into the special allocation class. 1199Blocks smaller than or equal to this 1200value will be assigned to the special allocation class while greater blocks 1201will be assigned to the regular class. 1202Valid values are zero or a power of two from 512 up to 1048576 (1 MiB). 1203The default size is 0 which means no small file blocks 1204will be allocated in the special class. 1205.Pp 1206Before setting this property, a special class vdev must be added to the 1207pool. 1208See 1209.Xr zpoolconcepts 7 1210for more details on the special allocation class. 1211.It Sy mountpoint Ns = Ns Pa path Ns | Ns Sy none Ns | Ns Sy legacy 1212Controls the mount point used for this file system. 1213See the 1214.Sx Mount Points 1215section of 1216.Xr zfsconcepts 7 1217for more information on how this property is used. 1218.Pp 1219When the 1220.Sy mountpoint 1221property is changed for a file system, the file system and any children that 1222inherit the mount point are unmounted. 1223If the new value is 1224.Sy legacy , 1225then they remain unmounted. 1226Otherwise, they are automatically remounted in the new location if the property 1227was previously 1228.Sy legacy 1229or 1230.Sy none , 1231or if they were mounted before the property was changed. 1232In addition, any shared file systems are unshared and shared in the new 1233location. 1234.It Sy nbmand Ns = Ns Sy on Ns | Ns Sy off 1235Controls whether the file system should be mounted with 1236.Sy nbmand 1237.Pq Non-blocking mandatory locks . 1238This is used for SMB clients. 1239Changes to this property only take effect when the file system is umounted and 1240remounted. 1241Support for these locks is scarce and not described by POSIX. 1242.It Sy overlay Ns = Ns Sy on Ns | Ns Sy off 1243Allow mounting on a busy directory or a directory which already contains 1244files or directories. 1245This is the default mount behavior for Linux and 1246.Fx 1247file systems. 1248On these platforms the property is 1249.Sy on 1250by default. 1251Set to 1252.Sy off 1253to disable overlay mounts for consistency with OpenZFS on other platforms. 1254.It Sy primarycache Ns = Ns Sy all Ns | Ns Sy none Ns | Ns Sy metadata 1255Controls what is cached in the primary cache 1256.Pq ARC . 1257If this property is set to 1258.Sy all , 1259then both user data and metadata is cached. 1260If this property is set to 1261.Sy none , 1262then neither user data nor metadata is cached. 1263If this property is set to 1264.Sy metadata , 1265then only metadata is cached. 1266The default value is 1267.Sy all . 1268.It Sy quota Ns = Ns Ar size Ns | Ns Sy none 1269Limits the amount of space a dataset and its descendents can consume. 1270This property enforces a hard limit on the amount of space used. 1271This includes all space consumed by descendents, including file systems and 1272snapshots. 1273Setting a quota on a descendent of a dataset that already has a quota does not 1274override the ancestor's quota, but rather imposes an additional limit. 1275.Pp 1276Quotas cannot be set on volumes, as the 1277.Sy volsize 1278property acts as an implicit quota. 1279.It Sy snapshot_limit Ns = Ns Ar count Ns | Ns Sy none 1280Limits the number of snapshots that can be created on a dataset and its 1281descendents. 1282Setting a 1283.Sy snapshot_limit 1284on a descendent of a dataset that already has a 1285.Sy snapshot_limit 1286does not override the ancestor's 1287.Sy snapshot_limit , 1288but rather imposes an additional limit. 1289The limit is not enforced if the user is allowed to change the limit. 1290For example, this means that recursive snapshots taken from the global zone are 1291counted against each delegated dataset within a zone. 1292This feature must be enabled to be used 1293.Po see 1294.Xr zpool-features 7 1295.Pc . 1296.It Sy userquota@ Ns Ar user Ns = Ns Ar size Ns | Ns Sy none 1297Limits the amount of space consumed by the specified user. 1298User space consumption is identified by the 1299.Sy userspace@ Ns Ar user 1300property. 1301.Pp 1302Enforcement of user quotas may be delayed by several seconds. 1303This delay means that a user might exceed their quota before the system notices 1304that they are over quota and begins to refuse additional writes with the 1305.Er EDQUOT 1306error message. 1307See the 1308.Nm zfs Cm userspace 1309command for more information. 1310.Pp 1311Unprivileged users can only access their own groups' space usage. 1312The root user, or a user who has been granted the 1313.Sy userquota 1314privilege with 1315.Nm zfs Cm allow , 1316can get and set everyone's quota. 1317.Pp 1318This property is not available on volumes, on file systems before version 4, or 1319on pools before version 15. 1320The 1321.Sy userquota@ Ns Ar … 1322properties are not displayed by 1323.Nm zfs Cm get Sy all . 1324The user's name must be appended after the 1325.Sy @ 1326symbol, using one of the following forms: 1327.Bl -bullet -compact -offset 4n 1328.It 1329POSIX name 1330.Pq Qq joe 1331.It 1332POSIX numeric ID 1333.Pq Qq 789 1334.It 1335SID name 1336.Pq Qq joe.smith@mydomain 1337.It 1338SID numeric ID 1339.Pq Qq S-1-123-456-789 1340.El 1341.Pp 1342Files created on Linux always have POSIX owners. 1343.It Sy userobjquota@ Ns Ar user Ns = Ns Ar size Ns | Ns Sy none 1344The 1345.Sy userobjquota 1346is similar to 1347.Sy userquota 1348but it limits the number of objects a user can create. 1349Please refer to 1350.Sy userobjused 1351for more information about how objects are counted. 1352.It Sy groupquota@ Ns Ar group Ns = Ns Ar size Ns | Ns Sy none 1353Limits the amount of space consumed by the specified group. 1354Group space consumption is identified by the 1355.Sy groupused@ Ns Ar group 1356property. 1357.Pp 1358Unprivileged users can access only their own groups' space usage. 1359The root user, or a user who has been granted the 1360.Sy groupquota 1361privilege with 1362.Nm zfs Cm allow , 1363can get and set all groups' quotas. 1364.It Sy groupobjquota@ Ns Ar group Ns = Ns Ar size Ns | Ns Sy none 1365The 1366.Sy groupobjquota 1367is similar to 1368.Sy groupquota 1369but it limits number of objects a group can consume. 1370Please refer to 1371.Sy userobjused 1372for more information about how objects are counted. 1373.It Sy projectquota@ Ns Ar project Ns = Ns Ar size Ns | Ns Sy none 1374Limits the amount of space consumed by the specified project. 1375Project space consumption is identified by the 1376.Sy projectused@ Ns Ar project 1377property. 1378Please refer to 1379.Sy projectused 1380for more information about how project is identified and set/changed. 1381.Pp 1382The root user, or a user who has been granted the 1383.Sy projectquota 1384privilege with 1385.Nm zfs allow , 1386can access all projects' quota. 1387.It Sy projectobjquota@ Ns Ar project Ns = Ns Ar size Ns | Ns Sy none 1388The 1389.Sy projectobjquota 1390is similar to 1391.Sy projectquota 1392but it limits number of objects a project can consume. 1393Please refer to 1394.Sy userobjused 1395for more information about how objects are counted. 1396.It Sy readonly Ns = Ns Sy on Ns | Ns Sy off 1397Controls whether this dataset can be modified. 1398The default value is 1399.Sy off . 1400The values 1401.Sy on 1402and 1403.Sy off 1404are equivalent to the 1405.Sy ro 1406and 1407.Sy rw 1408mount options. 1409.Pp 1410This property can also be referred to by its shortened column name, 1411.Sy rdonly . 1412.It Sy recordsize Ns = Ns Ar size 1413Specifies a suggested block size for files in the file system. 1414This property is designed solely for use with database workloads that access 1415files in fixed-size records. 1416ZFS automatically tunes block sizes according to internal algorithms optimized 1417for typical access patterns. 1418.Pp 1419For databases that create very large files but access them in small random 1420chunks, these algorithms may be suboptimal. 1421Specifying a 1422.Sy recordsize 1423greater than or equal to the record size of the database can result in 1424significant performance gains. 1425Use of this property for general purpose file systems is strongly discouraged, 1426and may adversely affect performance. 1427.Pp 1428The size specified must be a power of two greater than or equal to 1429.Ar 512 B 1430and less than or equal to 1431.Ar 128 KiB . 1432If the 1433.Sy large_blocks 1434feature is enabled on the pool, the size may be up to 1435.Ar 1 MiB . 1436See 1437.Xr zpool-features 7 1438for details on ZFS feature flags. 1439.Pp 1440Changing the file system's 1441.Sy recordsize 1442affects only files created afterward; existing files are unaffected. 1443.Pp 1444This property can also be referred to by its shortened column name, 1445.Sy recsize . 1446.It Sy redundant_metadata Ns = Ns Sy all Ns | Ns Sy most 1447Controls what types of metadata are stored redundantly. 1448ZFS stores an extra copy of metadata, so that if a single block is corrupted, 1449the amount of user data lost is limited. 1450This extra copy is in addition to any redundancy provided at the pool level 1451.Pq e.g. by mirroring or RAID-Z , 1452and is in addition to an extra copy specified by the 1453.Sy copies 1454property 1455.Pq up to a total of 3 copies . 1456For example if the pool is mirrored, 1457.Sy copies Ns = Ns 2 , 1458and 1459.Sy redundant_metadata Ns = Ns Sy most , 1460then ZFS stores 6 copies of most metadata, and 4 copies of data and some 1461metadata. 1462.Pp 1463When set to 1464.Sy all , 1465ZFS stores an extra copy of all metadata. 1466If a single on-disk block is corrupt, at worst a single block of user data 1467.Po which is 1468.Sy recordsize 1469bytes long 1470.Pc 1471can be lost. 1472.Pp 1473When set to 1474.Sy most , 1475ZFS stores an extra copy of most types of metadata. 1476This can improve performance of random writes, because less metadata must be 1477written. 1478In practice, at worst about 100 blocks 1479.Po of 1480.Sy recordsize 1481bytes each 1482.Pc 1483of user data can be lost if a single on-disk block is corrupt. 1484The exact behavior of which metadata blocks are stored redundantly may change in 1485future releases. 1486.Pp 1487The default value is 1488.Sy all . 1489.It Sy refquota Ns = Ns Ar size Ns | Ns Sy none 1490Limits the amount of space a dataset can consume. 1491This property enforces a hard limit on the amount of space used. 1492This hard limit does not include space used by descendents, including file 1493systems and snapshots. 1494.It Sy refreservation Ns = Ns Ar size Ns | Ns Sy none Ns | Ns Sy auto 1495The minimum amount of space guaranteed to a dataset, not including its 1496descendents. 1497When the amount of space used is below this value, the dataset is treated as if 1498it were taking up the amount of space specified by 1499.Sy refreservation . 1500The 1501.Sy refreservation 1502reservation is accounted for in the parent datasets' space used, and counts 1503against the parent datasets' quotas and reservations. 1504.Pp 1505If 1506.Sy refreservation 1507is set, a snapshot is only allowed if there is enough free pool space outside of 1508this reservation to accommodate the current number of 1509.Qq referenced 1510bytes in the dataset. 1511.Pp 1512If 1513.Sy refreservation 1514is set to 1515.Sy auto , 1516a volume is thick provisioned 1517.Po or 1518.Qq not sparse 1519.Pc . 1520.Sy refreservation Ns = Ns Sy auto 1521is only supported on volumes. 1522See 1523.Sy volsize 1524in the 1525.Sx Native Properties 1526section for more information about sparse volumes. 1527.Pp 1528This property can also be referred to by its shortened column name, 1529.Sy refreserv . 1530.It Sy relatime Ns = Ns Sy on Ns | Ns Sy off 1531Controls the manner in which the access time is updated when 1532.Sy atime Ns = Ns Sy on 1533is set. 1534Turning this property on causes the access time to be updated relative 1535to the modify or change time. 1536Access time is only updated if the previous 1537access time was earlier than the current modify or change time or if the 1538existing access time hasn't been updated within the past 24 hours. 1539The default value is 1540.Sy off . 1541The values 1542.Sy on 1543and 1544.Sy off 1545are equivalent to the 1546.Sy relatime 1547and 1548.Sy norelatime 1549mount options. 1550.It Sy reservation Ns = Ns Ar size Ns | Ns Sy none 1551The minimum amount of space guaranteed to a dataset and its descendants. 1552When the amount of space used is below this value, the dataset is treated as if 1553it were taking up the amount of space specified by its reservation. 1554Reservations are accounted for in the parent datasets' space used, and count 1555against the parent datasets' quotas and reservations. 1556.Pp 1557This property can also be referred to by its shortened column name, 1558.Sy reserv . 1559.It Sy secondarycache Ns = Ns Sy all Ns | Ns Sy none Ns | Ns Sy metadata 1560Controls what is cached in the secondary cache 1561.Pq L2ARC . 1562If this property is set to 1563.Sy all , 1564then both user data and metadata is cached. 1565If this property is set to 1566.Sy none , 1567then neither user data nor metadata is cached. 1568If this property is set to 1569.Sy metadata , 1570then only metadata is cached. 1571The default value is 1572.Sy all . 1573.It Sy setuid Ns = Ns Sy on Ns | Ns Sy off 1574Controls whether the setuid bit is respected for the file system. 1575The default value is 1576.Sy on . 1577The values 1578.Sy on 1579and 1580.Sy off 1581are equivalent to the 1582.Sy suid 1583and 1584.Sy nosuid 1585mount options. 1586.It Sy sharesmb Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Ar opts 1587Controls whether the file system is shared by using 1588.Sy Samba USERSHARES 1589and what options are to be used. 1590Otherwise, the file system is automatically shared and unshared with the 1591.Nm zfs Cm share 1592and 1593.Nm zfs Cm unshare 1594commands. 1595If the property is set to on, the 1596.Xr net 8 1597command is invoked to create a 1598.Sy USERSHARE . 1599.Pp 1600Because SMB shares requires a resource name, a unique resource name is 1601constructed from the dataset name. 1602The constructed name is a copy of the 1603dataset name except that the characters in the dataset name, which would be 1604invalid in the resource name, are replaced with underscore (_) characters. 1605Linux does not currently support additional options which might be available 1606on Solaris. 1607.Pp 1608If the 1609.Sy sharesmb 1610property is set to 1611.Sy off , 1612the file systems are unshared. 1613.Pp 1614The share is created with the ACL (Access Control List) "Everyone:F" ("F" 1615stands for "full permissions", i.e. read and write permissions) and no guest 1616access (which means Samba must be able to authenticate a real user \(em 1617.Xr passwd 5 Ns / Ns Xr shadow 5 Ns - , 1618LDAP- or 1619.Xr smbpasswd 5 Ns -based ) 1620by default. 1621This means that any additional access control 1622(disallow specific user specific access etc) must be done on the underlying file system. 1623.It Sy sharenfs Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Ar opts 1624Controls whether the file system is shared via NFS, and what options are to be 1625used. 1626A file system with a 1627.Sy sharenfs 1628property of 1629.Sy off 1630is managed with the 1631.Xr exportfs 8 1632command and entries in the 1633.Pa /etc/exports 1634file. 1635Otherwise, the file system is automatically shared and unshared with the 1636.Nm zfs Cm share 1637and 1638.Nm zfs Cm unshare 1639commands. 1640If the property is set to 1641.Sy on , 1642the dataset is shared using the default options: 1643.Dl sec=sys,rw,crossmnt,no_subtree_check 1644.Pp 1645Please note that the options are comma-separated, unlike those found in 1646.Xr exports 5 . 1647This is done to negate the need for quoting, as well as to make parsing 1648with scripts easier. 1649.Pp 1650See 1651.Xr exports 5 1652for the meaning of the default options. 1653Otherwise, the 1654.Xr exportfs 8 1655command is invoked with options equivalent to the contents of this property. 1656.Pp 1657When the 1658.Sy sharenfs 1659property is changed for a dataset, the dataset and any children inheriting the 1660property are re-shared with the new options, only if the property was previously 1661.Sy off , 1662or if they were shared before the property was changed. 1663If the new property is 1664.Sy off , 1665the file systems are unshared. 1666.It Sy logbias Ns = Ns Sy latency Ns | Ns Sy throughput 1667Provide a hint to ZFS about handling of synchronous requests in this dataset. 1668If 1669.Sy logbias 1670is set to 1671.Sy latency 1672.Pq the default , 1673ZFS will use pool log devices 1674.Pq if configured 1675to handle the requests at low latency. 1676If 1677.Sy logbias 1678is set to 1679.Sy throughput , 1680ZFS will not use configured pool log devices. 1681ZFS will instead optimize synchronous operations for global pool throughput and 1682efficient use of resources. 1683.It Sy snapdev Ns = Ns Sy hidden Ns | Ns Sy visible 1684Controls whether the volume snapshot devices under 1685.Pa /dev/zvol/ Ns Aq Ar pool 1686are hidden or visible. 1687The default value is 1688.Sy hidden . 1689.It Sy snapdir Ns = Ns Sy hidden Ns | Ns Sy visible 1690Controls whether the 1691.Pa .zfs 1692directory is hidden or visible in the root of the file system as discussed in 1693the 1694.Sx Snapshots 1695section of 1696.Xr zfsconcepts 7 . 1697The default value is 1698.Sy hidden . 1699.It Sy sync Ns = Ns Sy standard Ns | Ns Sy always Ns | Ns Sy disabled 1700Controls the behavior of synchronous requests 1701.Pq e.g. fsync, O_DSYNC . 1702.Sy standard 1703is the POSIX-specified behavior of ensuring all synchronous requests 1704are written to stable storage and all devices are flushed to ensure 1705data is not cached by device controllers 1706.Pq this is the default . 1707.Sy always 1708causes every file system transaction to be written and flushed before its 1709system call returns. 1710This has a large performance penalty. 1711.Sy disabled 1712disables synchronous requests. 1713File system transactions are only committed to stable storage periodically. 1714This option will give the highest performance. 1715However, it is very dangerous as ZFS would be ignoring the synchronous 1716transaction demands of applications such as databases or NFS. 1717Administrators should only use this option when the risks are understood. 1718.It Sy version Ns = Ns Ar N Ns | Ns Sy current 1719The on-disk version of this file system, which is independent of the pool 1720version. 1721This property can only be set to later supported versions. 1722See the 1723.Nm zfs Cm upgrade 1724command. 1725.It Sy volsize Ns = Ns Ar size 1726For volumes, specifies the logical size of the volume. 1727By default, creating a volume establishes a reservation of equal size. 1728For storage pools with a version number of 9 or higher, a 1729.Sy refreservation 1730is set instead. 1731Any changes to 1732.Sy volsize 1733are reflected in an equivalent change to the reservation 1734.Pq or Sy refreservation . 1735The 1736.Sy volsize 1737can only be set to a multiple of 1738.Sy volblocksize , 1739and cannot be zero. 1740.Pp 1741The reservation is kept equal to the volume's logical size to prevent unexpected 1742behavior for consumers. 1743Without the reservation, the volume could run out of space, resulting in 1744undefined behavior or data corruption, depending on how the volume is used. 1745These effects can also occur when the volume size is changed while it is in use 1746.Pq particularly when shrinking the size . 1747Extreme care should be used when adjusting the volume size. 1748.Pp 1749Though not recommended, a 1750.Qq sparse volume 1751.Po also known as 1752.Qq thin provisioned 1753.Pc 1754can be created by specifying the 1755.Fl s 1756option to the 1757.Nm zfs Cm create Fl V 1758command, or by changing the value of the 1759.Sy refreservation 1760property 1761.Po or 1762.Sy reservation 1763property on pool version 8 or earlier 1764.Pc 1765after the volume has been created. 1766A 1767.Qq sparse volume 1768is a volume where the value of 1769.Sy refreservation 1770is less than the size of the volume plus the space required to store its 1771metadata. 1772Consequently, writes to a sparse volume can fail with 1773.Er ENOSPC 1774when the pool is low on space. 1775For a sparse volume, changes to 1776.Sy volsize 1777are not reflected in the 1778.Sy refreservation . 1779A volume that is not sparse is said to be 1780.Qq thick provisioned . 1781A sparse volume can become thick provisioned by setting 1782.Sy refreservation 1783to 1784.Sy auto . 1785.It Sy volmode Ns = Ns Sy default Ns | Ns Sy full Ns | Ns Sy geom Ns | Ns Sy dev Ns | Ns Sy none 1786This property specifies how volumes should be exposed to the OS. 1787Setting it to 1788.Sy full 1789exposes volumes as fully fledged block devices, providing maximal 1790functionality. 1791The value 1792.Sy geom 1793is just an alias for 1794.Sy full 1795and is kept for compatibility. 1796Setting it to 1797.Sy dev 1798hides its partitions. 1799Volumes with property set to 1800.Sy none 1801are not exposed outside ZFS, but can be snapshotted, cloned, replicated, etc, 1802that can be suitable for backup purposes. 1803Value 1804.Sy default 1805means that volumes exposition is controlled by system-wide tunable 1806.Sy zvol_volmode , 1807where 1808.Sy full , 1809.Sy dev 1810and 1811.Sy none 1812are encoded as 1, 2 and 3 respectively. 1813The default value is 1814.Sy full . 1815.It Sy vscan Ns = Ns Sy on Ns | Ns Sy off 1816Controls whether regular files should be scanned for viruses when a file is 1817opened and closed. 1818In addition to enabling this property, the virus scan service must also be 1819enabled for virus scanning to occur. 1820The default value is 1821.Sy off . 1822This property is not used by OpenZFS. 1823.It Sy xattr Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Sy sa 1824Controls whether extended attributes are enabled for this file system. 1825Two styles of extended attributes are supported: either directory-based 1826or system-attribute-based. 1827.Pp 1828The default value of 1829.Sy on 1830enables directory-based extended attributes. 1831This style of extended attribute imposes no practical limit 1832on either the size or number of attributes which can be set on a file. 1833Although under Linux the 1834.Xr getxattr 2 1835and 1836.Xr setxattr 2 1837system calls limit the maximum size to 1838.Sy 64K . 1839This is the most compatible 1840style of extended attribute and is supported by all ZFS implementations. 1841.Pp 1842System-attribute-based xattrs can be enabled by setting the value to 1843.Sy sa . 1844The key advantage of this type of xattr is improved performance. 1845Storing extended attributes as system attributes 1846significantly decreases the amount of disk I/O required. 1847Up to 1848.Sy 64K 1849of data may be stored per-file in the space reserved for system attributes. 1850If there is not enough space available for an extended attribute 1851then it will be automatically written as a directory-based xattr. 1852System-attribute-based extended attributes are not accessible 1853on platforms which do not support the 1854.Sy xattr Ns = Ns Sy sa 1855feature. 1856OpenZFS supports 1857.Sy xattr Ns = Ns Sy sa 1858on both 1859.Fx 1860and Linux. 1861.Pp 1862The use of system-attribute-based xattrs is strongly encouraged for users of 1863SELinux or POSIX ACLs. 1864Both of these features heavily rely on extended 1865attributes and benefit significantly from the reduced access time. 1866.Pp 1867The values 1868.Sy on 1869and 1870.Sy off 1871are equivalent to the 1872.Sy xattr 1873and 1874.Sy noxattr 1875mount options. 1876.It Sy jailed Ns = Ns Sy off Ns | Ns Sy on 1877Controls whether the dataset is managed from a jail. 1878See 1879.Xr zfs-jail 8 1880for more information. 1881Jails are a 1882.Fx 1883feature and are not relevant on other platforms. 1884The default value is 1885.Sy off . 1886.It Sy zoned Ns = Ns Sy on Ns | Ns Sy off 1887Controls whether the dataset is managed from a non-global zone. 1888Zones are a Solaris feature and are not relevant on other platforms. 1889The default value is 1890.Sy off . 1891.El 1892.Pp 1893The following three properties cannot be changed after the file system is 1894created, and therefore, should be set when the file system is created. 1895If the properties are not set with the 1896.Nm zfs Cm create 1897or 1898.Nm zpool Cm create 1899commands, these properties are inherited from the parent dataset. 1900If the parent dataset lacks these properties due to having been created prior to 1901these features being supported, the new file system will have the default values 1902for these properties. 1903.Bl -tag -width "" 1904.It Xo 1905.Sy casesensitivity Ns = Ns Sy sensitive Ns | Ns 1906.Sy insensitive Ns | Ns Sy mixed 1907.Xc 1908Indicates whether the file name matching algorithm used by the file system 1909should be case-sensitive, case-insensitive, or allow a combination of both 1910styles of matching. 1911The default value for the 1912.Sy casesensitivity 1913property is 1914.Sy sensitive . 1915Traditionally, 1916.Ux 1917and POSIX file systems have case-sensitive file names. 1918.Pp 1919The 1920.Sy mixed 1921value for the 1922.Sy casesensitivity 1923property indicates that the file system can support requests for both 1924case-sensitive and case-insensitive matching behavior. 1925Currently, case-insensitive matching behavior on a file system that supports 1926mixed behavior is limited to the SMB server product. 1927For more information about the 1928.Sy mixed 1929value behavior, see the "ZFS Administration Guide". 1930.It Xo 1931.Sy normalization Ns = Ns Sy none Ns | Ns Sy formC Ns | Ns 1932.Sy formD Ns | Ns Sy formKC Ns | Ns Sy formKD 1933.Xc 1934Indicates whether the file system should perform a 1935.Sy unicode 1936normalization of file names whenever two file names are compared, and which 1937normalization algorithm should be used. 1938File names are always stored unmodified, names are normalized as part of any 1939comparison process. 1940If this property is set to a legal value other than 1941.Sy none , 1942and the 1943.Sy utf8only 1944property was left unspecified, the 1945.Sy utf8only 1946property is automatically set to 1947.Sy on . 1948The default value of the 1949.Sy normalization 1950property is 1951.Sy none . 1952This property cannot be changed after the file system is created. 1953.It Sy utf8only Ns = Ns Sy on Ns | Ns Sy off 1954Indicates whether the file system should reject file names that include 1955characters that are not present in the 1956.Sy UTF-8 1957character code set. 1958If this property is explicitly set to 1959.Sy off , 1960the normalization property must either not be explicitly set or be set to 1961.Sy none . 1962The default value for the 1963.Sy utf8only 1964property is 1965.Sy off . 1966This property cannot be changed after the file system is created. 1967.El 1968.Pp 1969The 1970.Sy casesensitivity , 1971.Sy normalization , 1972and 1973.Sy utf8only 1974properties are also new permissions that can be assigned to non-privileged users 1975by using the ZFS delegated administration feature. 1976. 1977.Ss Temporary Mount Point Properties 1978When a file system is mounted, either through 1979.Xr mount 8 1980for legacy mounts or the 1981.Nm zfs Cm mount 1982command for normal file systems, its mount options are set according to its 1983properties. 1984The correlation between properties and mount options is as follows: 1985.Bl -tag -compact -offset Ds -width "rootcontext=" 1986.It Sy atime 1987atime/noatime 1988.It Sy canmount 1989auto/noauto 1990.It Sy devices 1991dev/nodev 1992.It Sy exec 1993exec/noexec 1994.It Sy readonly 1995ro/rw 1996.It Sy relatime 1997relatime/norelatime 1998.It Sy setuid 1999suid/nosuid 2000.It Sy xattr 2001xattr/noxattr 2002.It Sy nbmand 2003mand/nomand 2004.It Sy context Ns = 2005context= 2006.It Sy fscontext Ns = 2007fscontext= 2008.It Sy defcontext Ns = 2009defcontext= 2010.It Sy rootcontext Ns = 2011rootcontext= 2012.El 2013.Pp 2014In addition, these options can be set on a per-mount basis using the 2015.Fl o 2016option, without affecting the property that is stored on disk. 2017The values specified on the command line override the values stored in the 2018dataset. 2019The 2020.Sy nosuid 2021option is an alias for 2022.Sy nodevices , Ns Sy nosetuid . 2023These properties are reported as 2024.Qq temporary 2025by the 2026.Nm zfs Cm get 2027command. 2028If the properties are changed while the dataset is mounted, the new setting 2029overrides any temporary settings. 2030. 2031.Ss User Properties 2032In addition to the standard native properties, ZFS supports arbitrary user 2033properties. 2034User properties have no effect on ZFS behavior, but applications or 2035administrators can use them to annotate datasets 2036.Pq file systems, volumes, and snapshots . 2037.Pp 2038User property names must contain a colon 2039.Pq Qq Sy \&: 2040character to distinguish them from native properties. 2041They may contain lowercase letters, numbers, and the following punctuation 2042characters: colon 2043.Pq Qq Sy \&: , 2044dash 2045.Pq Qq Sy - , 2046period 2047.Pq Qq Sy \&. , 2048and underscore 2049.Pq Qq Sy _ . 2050The expected convention is that the property name is divided into two portions 2051such as 2052.Ar module : Ns Ar property , 2053but this namespace is not enforced by ZFS. 2054User property names can be at most 256 characters, and cannot begin with a dash 2055.Pq Qq Sy - . 2056.Pp 2057When making programmatic use of user properties, it is strongly suggested to use 2058a reversed DNS domain name for the 2059.Ar module 2060component of property names to reduce the chance that two 2061independently-developed packages use the same property name for different 2062purposes. 2063.Pp 2064The values of user properties are arbitrary strings, are always inherited, and 2065are never validated. 2066All of the commands that operate on properties 2067.Po Nm zfs Cm list , 2068.Nm zfs Cm get , 2069.Nm zfs Cm set , 2070and so forth 2071.Pc 2072can be used to manipulate both native properties and user properties. 2073Use the 2074.Nm zfs Cm inherit 2075command to clear a user property. 2076If the property is not defined in any parent dataset, it is removed entirely. 2077Property values are limited to 8192 bytes. 2078