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.
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.
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]
20 .\" Copyright (c) 2007 Sun Microsystems, Inc. All Rights Reserved.
21 .TH zfs 1M "16 Mar 2007" "SunOS 5.11" "System Administration Commands"
23 zfs \- configures ZFS file systems
32 \fBzfs\fR \fBcreate\fR [[\fB-o\fR property=\fIvalue\fR]]... \fIfilesystem\fR
37 \fBzfs\fR \fBcreate\fR [\fB-s\fR] [\fB-b\fR \fIblocksize\fR] [[\fB-o\fR property=\fIvalue\fR]]... \fB-V\fR \fIsize\fR \fIvolume\fR
42 \fBzfs\fR \fBdestroy\fR [\fB-rRf\fR] \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR
47 \fBzfs\fR \fBclone\fR \fIsnapshot\fR \fIfilesystem\fR|\fIvolume\fR
52 \fBzfs\fR \fBpromote\fR \fIfilesystem\fR
57 \fBzfs\fR \fBrename\fR \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR
58 [\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR]
63 \fBzfs\fR \fBsnapshot\fR [\fB-r\fR] \fIfilesystem@name\fR|\fIvolume@name\fR
68 \fBzfs\fR \fBrollback\fR [\fB-rRf\fR] \fIsnapshot\fR
73 \fBzfs\fR \fBlist\fR [\fB-rH\fR] [\fB-o\fR \fIprop\fR[,\fIprop\fR] ]... [ \fB-t\fR \fItype\fR[,\fItype\fR]...]
74 [ \fB-s\fR \fIprop\fR [\fB-s\fR \fIprop\fR]... [ \fB-S\fR \fIprop\fR [\fB-S\fR \fIprop\fR]...
75 [\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR|\fI/pathname\fR|.\fI/pathname\fR ...
80 \fBzfs\fR \fBset\fR \fIproperty\fR=\fIvalue\fR \fIfilesystem\fR|\fIvolume\fR ...
85 \fBzfs\fR \fBget\fR [\fB-rHp\fR] [\fB-o\fR \fIfield\fR[,\fIfield\fR]...]
86 [\fB-s\fR \fIsource\fR[,\fIsource\fR]...] \fIall\fR | \fIproperty\fR[,\fIproperty\fR]...
87 \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR ...
92 \fBzfs\fR \fBinherit\fR [\fB-r\fR] \fIproperty\fR \fIfilesystem\fR|\fIvolume\fR... ...
102 \fBzfs\fR \fBmount\fR [\fB-o \fIoptions\fR\fR] [\fB-O\fR] \fB-a\fR
107 \fBzfs\fR \fBmount\fR [\fB-o \fIoptions\fR\fR] [\fB-O\fR] \fIfilesystem\fR
112 \fBzfs\fR \fBunmount\fR [\fB-f\fR] \fB-a\fR
117 \fBzfs\fR \fBunmount\fR [\fB-f\fR] \fB\fIfilesystem\fR|\fImountpoint\fR\fR
122 \fBzfs\fR \fBshare\fR \fB-a\fR
127 \fBzfs\fR \fBshare\fR \fIfilesystem\fR
132 \fBzfs\fR \fBunshare\fR [\fB-f\fR] \fB-a\fR
137 \fBzfs\fR \fBunshare\fR [\fB-f\fR] \fB\fIfilesystem\fR|\fImountpoint\fR\fR
142 \fBzfs\fR \fBsend\fR [\fB-i\fR \fIsnapshot1\fR] \fB\fIsnapshot2\fR\fR
147 \fBzfs\fR \fBreceive\fR [\fB-vnF\fR ] \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR
152 \fBzfs\fR \fBreceive\fR [\fB-vnF\fR ] \fB-d\fR \fB\fIfilesystem\fR\fR
156 \fBzfs\fR \fBjail\fR \fBjailid\fR \fB\fIfilesystem\fR\fR
160 \fBzfs\fR \fBunjail\fR \fBjailid\fR \fB\fIfilesystem\fR\fR
165 The \fBzfs\fR command configures \fBZFS\fR datasets within a \fBZFS\fR storage pool, as described in \fBzpool\fR(1M). A
166 dataset is identified by a unique path within the \fBZFS\fR namespace. For example:
170 pool/{filesystem,volume,snapshot}
176 where the maximum length of a dataset name is \fBMAXNAMELEN\fR (256 bytes).
178 A dataset can be one of the following:
183 \fB\fIfile system\fR\fR
187 A standard \fBPOSIX\fR file system. \fBZFS\fR file systems can be mounted within the standard file system namespace and behave like any other file system.
198 A logical volume exported as a raw or block device. This type of dataset should only be used under special circumstances. File systems are typically used in most environments. Volumes cannot be used in a non-global zone.
209 A read-only version of a file system or volume at a given point in time. It is specified as \fIfilesystem@name\fR or \fIvolume@name\fR.
212 .SS "ZFS File System Hierarchy"
214 A \fBZFS\fR storage pool is a logical collection of devices that provide space for datasets. A storage pool is also the root of the \fBZFS\fR file system hierarchy.
216 The root of the pool can be accessed as a file system, such as mounting and unmounting, taking snapshots, and setting properties. The physical storage characteristics, however, are managed by the \fBzpool\fR(1M) command.
218 See \fBzpool\fR(1M) for more information on creating and administering pools.
221 A snapshot is a read-only copy of a file system or volume. Snapshots can be created extremely quickly, and initially consume no additional space within the pool. As data within the active dataset changes, the snapshot consumes more data than would otherwise be shared with the active dataset.
223 Snapshots can have arbitrary names. Snapshots of volumes can be cloned or rolled back, but cannot be accessed independently.
225 File system snapshots can be accessed under the ".zfs/snapshot" directory in the root of the file system. Snapshots are automatically mounted on demand and may be unmounted at regular intervals. The visibility of the ".zfs" directory can be controlled by the "snapdir"
229 A clone is a writable volume or file system whose initial contents are the same as another dataset. As with snapshots, creating a clone is nearly instantaneous, and initially consumes no additional space.
231 Clones can only be created from a snapshot. When a snapshot is cloned, it creates an implicit dependency between the parent and child. Even though the clone is created somewhere else in the dataset hierarchy, the original snapshot cannot be destroyed as long as a clone exists. The "origin"
232 property exposes this dependency, and the \fBdestroy\fR command lists any such dependencies, if they exist.
234 The clone parent-child dependency relationship can be reversed by using the "\fBpromote\fR" subcommand. This causes the "origin" file system to become a clone of the specified file system, which makes it possible to destroy the file system that the clone
238 Creating a \fBZFS\fR file system is a simple operation, so the number of file systems per system will likely be numerous. To cope with this, \fBZFS\fR automatically manages mounting and unmounting file systems without the need to edit the \fB/etc/vfstab\fR file.
239 All automatically managed file systems are mounted by \fBZFS\fR at boot time.
241 By default, file systems are mounted under \fB/\fIpath\fR\fR, where \fIpath\fR is the name of the file system in the \fBZFS\fR namespace. Directories are created and destroyed as needed.
243 A file system can also have a mount point set in the "mountpoint" property. This directory is created as needed, and \fBZFS\fR automatically mounts the file system when the "\fBzfs mount -a\fR" command is invoked (without editing \fB/etc/vfstab\fR). The mountpoint property can be inherited, so if \fBpool/home\fR has a mount point of \fB/export/stuff\fR, then \fBpool/home/user\fR automatically inherits a mount point of \fB/export/stuff/user\fR.
245 A file system mountpoint property of "none" prevents the file system from being mounted.
247 If needed, \fBZFS\fR file systems can also be managed with traditional tools (\fBmount\fR, \fBumount\fR, \fB/etc/vfstab\fR). If a file system's mount point is set to "legacy", \fBZFS\fR makes no attempt to manage
248 the file system, and the administrator is responsible for mounting and unmounting the file system.
251 A \fBZFS\fR file system can be added to a non-global zone by using zonecfg's "\fBadd fs\fR" subcommand. A \fBZFS\fR file system that is added to a non-global zone must have its mountpoint property set to legacy.
253 The physical properties of an added file system are controlled by the global administrator. However, the zone administrator can create, modify, or destroy files within the added file system, depending on how the file system is mounted.
255 A dataset can also be delegated to a non-global zone by using zonecfg's "\fBadd dataset\fR" subcommand. You cannot delegate a dataset to one zone and the children of the same dataset to another zone. The zone administrator can change properties of the dataset or
256 any of its children. However, the "quota" property is controlled by the global administrator.
258 A \fBZFS\fR volume can be added as a device to a non-global zone by using zonecfg's "\fBadd device\fR" subcommand. However, its physical properties can only be modified by the global administrator.
260 For more information about \fBzonecfg\fR syntax, see \fBzonecfg\fR(1M).
262 After a dataset is delegated to a non-global zone, the "zoned" property is automatically set. A zoned file system cannot be mounted in the global zone, since the zone administrator might have to set the mount point to an unacceptable value.
264 The global administrator can forcibly clear the "zoned" property, though this should be done with extreme care. The global administrator should verify that all the mount points are acceptable before clearing the property.
265 .SS "Native Properties"
267 Properties are divided into two types, native properties and user defined properties. Native properties either export internal statistics or control \fBZFS\fR behavior. In addition, native properties are either editable or read-only. User properties have no effect on \fBZFS\fR behavior,
268 but you can use them to annotate datasets in a way that is meaningful in your environment. For more information about user properties, see the "User Properties" section.
270 Every dataset has a set of properties that export statistics about the dataset as well as control various behavior. Properties are inherited from the parent unless overridden by the child. Snapshot properties can not be edited; they always inherit their inheritable properties. Properties
271 that are not applicable to snapshots are not displayed.
273 The values of numeric properties can be specified using the following human-readable suffixes (for example, "k", "KB", "M", "Gb", etc, up to Z for zettabyte). The following are all valid (and equal) specifications:
277 "1536M", "1.5g", "1.50GB".
283 The values of non-numeric properties are case sensitive and must be lowercase, except for "mountpoint" and "sharenfs".
285 The first set of properties consist of read-only statistics about the dataset. These properties cannot be set, nor are they inherited. Native properties apply to all dataset types unless otherwise noted.
294 The type of dataset: "filesystem", "volume", "snapshot", or "clone".
305 The time this dataset was created.
316 The amount of space consumed by this dataset and all its descendants. This is the value that is checked against this dataset's quota and reservation. The space used does not include this dataset's reservation, but does take into account the reservations of any descendant datasets.
317 The amount of space that a dataset consumes from its parent, as well as the amount of space that will be freed if this dataset is recursively destroyed, is the greater of its space used and its reservation.
319 When snapshots (see the "Snapshots" section) are created, their space is initially shared between the snapshot and the file system, and possibly with previous snapshots. As the file system changes, space that was previously shared becomes unique to the snapshot, and counted in
320 the snapshot's space used. Additionally, deleting snapshots can increase the amount of space unique to (and used by) other snapshots.
322 The amount of space used, available, or referenced does not take into account pending changes. Pending changes are generally accounted for within a few seconds. Committing a change to a disk using \fBfsync\fR(3c) or \fBO_SYNC\fR does not necessarily guarantee that the space usage information is updated immediately.
333 The amount of space available to the dataset and all its children, assuming that there is no other activity in the pool. Because space is shared within a pool, availability can be limited by any number of factors, including physical pool size, quotas, reservations, or other datasets
336 This property can also be referred to by its shortened column name, "avail".
347 The amount of data that is accessible by this dataset, which may or may not be shared with other datasets in the pool. When a snapshot or clone is created, it initially references the same amount of space as the file system or snapshot it was created from, since its contents are
350 This property can also be referred to by its shortened column name, "refer".
361 The compression ratio achieved for this dataset, expressed as a multiplier. Compression can be turned on by running "zfs set compression=on \fIdataset\fR". The default value is "off".
372 For file systems, indicates whether the file system is currently mounted. This property can be either "yes" or "no".
383 For cloned file systems or volumes, the snapshot from which the clone was created. The origin cannot be destroyed (even with the \fB-r\fR or \fB-f\fR options) so long as a clone exists.
387 The following two properties can be set to control the way space is allocated between datasets. These properties are not inherited, but do affect their descendants.
392 \fBquota=\fIsize\fR | \fInone\fR\fR
396 Limits the amount of space a dataset and its descendants can consume. This property enforces a hard limit on the amount of space used. This includes all space consumed by descendants, including file systems and snapshots. Setting a quota on a descendant of a dataset that already
397 has a quota does not override the ancestor's quota, but rather imposes an additional limit.
399 Quotas cannot be set on volumes, as the "volsize" property acts as an implicit quota.
406 \fBreservation=\fIsize\fR | \fInone\fR\fR
410 The minimum amount of space guaranteed to a dataset and its descendants. When the amount of space used is below this value, the dataset is treated as if it were taking up the amount of space specified by its reservation. Reservations are accounted for in the parent datasets' space
411 used, and count against the parent datasets' quotas and reservations.
413 This property can also be referred to by its shortened column name, "reserv".
420 \fBvolsize=\fIsize\fR\fR
424 For volumes, specifies the logical size of the volume. By default, creating a volume establishes a reservation of equal size. Any changes to \fBvolsize\fR are reflected in an equivalent change to the reservation. The \fBvolsize\fR can only be set to a
425 multiple of \fBvolblocksize\fR, and cannot be zero.
427 The reservation is kept equal to the volume's logical size to prevent unexpected behavior for consumers. Without the reservation, the volume could run out of space, resulting in undefined behavior or data corruption, depending on how the volume is used. These effects can also occur when
428 the volume size is changed while it is in use (particularly when shrinking the size). Extreme care should be used when adjusting the volume size.
430 Though not recommended, a "sparse volume" (also known as "thin provisioning") can be created by specifying the \fB-s\fR option to the "\fBzfs create -V\fR" command, or by changing the reservation after the volume has been created.
431 A "sparse volume" is a volume where the reservation is less then the volume size. Consequently, writes to a sparse volume can fail with \fBENOSPC\fR when the pool is low on space. For a sparse volume, changes to \fBvolsize\fR are not reflected in the reservation.
438 \fBvolblocksize=\fIblocksize\fR\fR
442 For volumes, specifies the block size of the volume. The \fBblocksize\fR cannot be changed once the volume has been written, so it should be set at volume creation time. The default \fBblocksize\fR for volumes is 8 Kbytes. Any power of 2 from 512 bytes
443 to 128 Kbytes is valid.
445 This property can also be referred to by its shortened column name, "volblock".
452 \fBrecordsize=\fIsize\fR\fR
456 Specifies a suggested block size for files in the file system. This property is designed solely for use with database workloads that access files in fixed-size records. \fBZFS\fR automatically tunes block sizes according to internal algorithms optimized for typical
459 For databases that create very large files but access them in small random chunks, these algorithms may be suboptimal. Specifying a "recordsize" greater than or equal to the record size of the database can result in significant performance gains. Use of this property for general
460 purpose file systems is strongly discouraged, and may adversely affect performance.
462 The size specified must be a power of two greater than or equal to 512 and less than or equal to 128 Kbytes.
464 Changing the file system's \fBrecordsize\fR only affects files created afterward; existing files are unaffected.
466 This property can also be referred to by its shortened column name, "recsize".
473 \fBmountpoint=\fIpath\fR | \fInone\fR | \fIlegacy\fR\fR
477 Controls the mount point used for this file system. See the "Mount Points" section for more information on how this property is used.
479 When the mountpoint property is changed for a file system, the file system and any children that inherit the mount point are unmounted. If the new value is "legacy", then they remain unmounted. Otherwise, they are automatically remounted in the new location if the property was
480 previously "legacy" or "none", or if they were mounted before the property was changed. In addition, any shared file systems are unshared and shared in the new location.
487 \fBsharenfs=\fIon\fR | \fIoff\fR | \fIopts\fR\fR
491 Controls whether the file system is shared via \fBNFS\fR, and what options are used. A file system with a sharenfs property of "off" is managed through traditional tools such as \fBshare\fR(1M), \fBunshare\fR(1M), and \fBdfstab\fR(4). Otherwise, the file system is automatically shared and unshared with the "\fBzfs share\fR" and "\fBzfs unshare\fR" commands. If the property is set to "on", the \fBshare\fR(1M) command is invoked with no options. Otherwise, the \fBshare\fR(1M) command is invoked with options equivalent to the contents of this property.
493 When the "sharenfs" property is changed for a dataset, the dataset and any children inheriting the property are re-shared with the new options, only if the property was previously "off", or if they were shared before the property was changed. If the new property is "off",
494 the file systems are unshared.
501 \fBshareiscsi=\fIon\fR | \fIoff\fR\fR
505 Like the "sharenfs" property, "shareiscsi" indicates whether a \fBZFS\fR volume is exported as an \fBiSCSI\fR target. The acceptable values for this property are "on", "off", and "type=disk".
506 The default value is "off". In the future, other target types might be supported. For example, "tape".
508 You might want to set "shareiscsi=on" for a file system so that all \fBZFS\fR volumes within the file system are shared by default. Setting this property on a file system has no direct effect, however.
515 \fBchecksum=\fIon\fR | \fIoff\fR | \fIfletcher2\fR, | \fIfletcher4\fR | \fIsha256\fR\fR
519 Controls the checksum used to verify data integrity. The default value is "on", which automatically selects an appropriate algorithm (currently, \fIfletcher2\fR, but this may change in future releases). The value "off" disables integrity
520 checking on user data. Disabling checksums is NOT a recommended practice.
527 \fBcompression=\fIon\fR | \fIoff\fR | \fIlzjb\fR | \fIgzip\fR | \fIgzip-N\fR\fR
531 Controls the compression algorithm used for this dataset. The "lzjb" compression algorithm is optimized for performance while providing decent data compression. Setting compression to "on" uses the "lzjb" compression algorithm. The "gzip"
532 compression algorithm uses the same compression as the \fBgzip\fR(1) command. You can specify the "gzip" level by using the value "gzip-\fIN\fR",
533 where \fIN\fR is an integer from 1 (fastest) to 9 (best compression ratio). Currently, "gzip" is equivalent to "gzip-6" (which is also the default for \fBgzip\fR(1)).
535 This property can also be referred to by its shortened column name "compress".
542 \fBatime=\fIon\fR | \fIoff\fR\fR
546 Controls whether the access time for files is updated when they are read. Turning this property off avoids producing write traffic when reading files and can result in significant performance gains, though it might confuse mailers and other similar utilities. The default value
554 \fBdevices=\fIon\fR | \fIoff\fR\fR
558 Controls whether device nodes can be opened on this file system. The default value is "on".
565 \fBexec=\fIon\fR | \fIoff\fR\fR
569 Controls whether processes can be executed from within this file system. The default value is "on".
576 \fBsetuid=\fIon\fR | \fIoff\fR\fR
580 Controls whether the set-\fBUID\fR bit is respected for the file system. The default value is "on".
587 \fBreadonly=\fIon\fR | \fIoff\fR\fR
591 Controls whether this dataset can be modified. The default value is "off".
593 This property can also be referred to by its shortened column name, "rdonly".
600 \fBzoned=\fIon\fR | \fIoff\fR\fR
604 Controls whether the dataset is managed from a non-global zone. See the "Zones" section for more information. The default value is "off".
611 \fBsnapdir=\fIhidden\fR | \fIvisible\fR\fR
615 Controls whether the ".zfs" directory is hidden or visible in the root of the file system as discussed in the "Snapshots" section. The default value is "hidden".
622 \fBaclmode=\fBdiscard\fR | \fBgroupmask\fR | \fBpassthrough\fR\fR
626 Controls how an \fBACL\fR is modified during \fBchmod\fR(2). A file system with an "aclmode" property of "\fBdiscard\fR"
627 deletes all \fBACL\fR entries that do not represent the mode of the file. An "aclmode" property of "\fBgroupmask\fR" (the default) reduces user or group permissions. The permissions are reduced, such that they are no greater than the group permission
628 bits, unless it is a user entry that has the same \fBUID\fR as the owner of the file or directory. In this case, the \fBACL\fR permissions are reduced so that they are no greater than owner permission bits. A file system with an "aclmode" property of "\fBpassthrough\fR" indicates that no changes will be made to the \fBACL\fR other than generating the necessary \fBACL\fR entries to represent the new mode of the file or directory.
635 \fBaclinherit=\fBdiscard\fR | \fBnoallow\fR | \fBsecure\fR | \fBpassthrough\fR\fR
639 Controls how \fBACL\fR entries are inherited when files and directories are created. A file system with an "aclinherit" property of "\fBdiscard\fR" does not inherit any \fBACL\fR entries. A file system with an "aclinherit"
640 property value of "\fBnoallow\fR" only inherits inheritable \fBACL\fR entries that specify "deny" permissions. The property value "\fBsecure\fR" (the default) removes the "\fBwrite_acl\fR" and "\fBwrite_owner\fR" permissions when the \fBACL\fR entry is inherited. A file system with an "aclinherit" property value of "\fBpassthrough\fR" inherits all inheritable \fBACL\fR entries without any modifications made to the \fBACL\fR entries when they are inherited.
647 \fBcanmount=\fBon\fR | \fBoff\fR\fR
651 If this property is set to "\fBoff\fR", the file system cannot be mounted, and is ignored by "\fBzfs mount -a\fR". This is similar to setting the "mountpoint" property to "\fBnone\fR", except
652 that the dataset still has a normal "mountpoint" property which can be inherited. This allows datasets to be used solely as a mechanism to inherit properties. One use case is to have two logically separate datasets have the same mountpoint, so that the children of both datasets appear
653 in the same directory, but may have different inherited characteristics. The default value is "\fBon\fR".
655 This property is not inherited.
662 \fBxattr=\fBon\fR | \fBoff\fR\fR
666 Controls whether extended attributes are enabled for this file system. The default value is "\fBon\fR".
673 \fBcopies=\fB1\fR | \fB2\fR | \fB3\fR\fR
677 Controls the number of copies of data stored for this dataset. These copies are in addition to any redundancy provided by the pool, for example, mirroring or raid-z. The copies are stored on different disks, if possible. The space used by multiple copies is charged to the associated
678 file and dataset, changing the "used" property and counting against quotas and reservations.
680 Changing this property only affects newly-written data. Therefore, set this property at file system creation time by using the "\fB-o\fR copies=" option.
687 \fBjailed=\fIon\fR | \fIoff\fR\fR
691 Controls whether the dataset is managed from within a jail. The default value is "off".
696 This read-only property, which is hidden, is used by the \fBiSCSI\fR target daemon to store persistent information, such as the \fBIQN\fR. It cannot be viewed or modified using the \fBzfs\fR command. The contents are not intended for external consumers.
697 .SS "Temporary Mount Point Properties"
699 When a file system is mounted, either through \fBmount\fR(1M) for legacy mounts or the "\fBzfs mount\fR" command for normal file systems,
700 its mount options are set according to its properties. The correlation between properties and mount options is as follows:
704 PROPERTY MOUNT OPTION
705 devices devices/nodevices
708 setuid setuid/nosetuid
715 In addition, these options can be set on a per-mount basis using the \fB-o\fR option, without affecting the property that is stored on disk. The values specified on the command line override the values stored in the dataset. The \fB-nosuid\fR option is an alias for "nodevices,nosetuid".
716 These properties are reported as "temporary" by the "\fBzfs get\fR" command. If the properties are changed while the dataset is mounted, the new setting overrides any temporary settings.
717 .SS "User Properties"
719 In addition to the standard native properties, \fBZFS\fR supports arbitrary user properties. User properties have no effect on \fBZFS\fR behavior, but applications or administrators can use them to annotate datasets.
721 User property names must contain a colon (":") character, to distinguish them from native properties. They might contain lowercase letters, numbers, and the following punctuation characters: colon (":"), dash ("-"), period ("."), and underscore
722 ("_"). The expected convention is that the property name is divided into two portions such as "\fImodule\fR:\fIproperty\fR", but this namespace is not enforced by \fBZFS\fR. User property names can be at most 256 characters,
723 and cannot begin with a dash ("-").
725 When making programmatic use of user properties, it is strongly suggested to use a reversed \fBDNS\fR domain name for the \fImodule\fR component of property names to reduce the chance that two independently-developed packages use the same property name for
726 different purposes. Property names beginning with "com.sun." are reserved for use by Sun Microsystems.
728 The values of user properties are arbitrary strings, are always inherited, and are never validated. All of the commands that operate on properties ("zfs list", "zfs get", "zfs set", etc.) can be used to manipulate both native properties and user properties.
729 Use the "\fBzfs inherit\fR" command to clear a user property . If the property is not defined in any parent dataset, it is removed entirely. Property values are limited to 1024 characters.
730 .SS "Volumes as Swap or Dump Devices"
732 To set up a swap area, create a \fBZFS\fR volume of a specific size and then enable swap on that device. For more information, see the EXAMPLES section.
734 Do not swap to a file on a \fBZFS\fR file system. A \fBZFS\fR swap file configuration is not supported.
736 Using a \fBZFS\fR volume as a dump device is not supported.
739 All subcommands that modify state are logged persistently to the pool in their original form.
748 Displays a help message.
755 \fB\fBzfs create\fR [[\fB-o\fR property=value]...] \fIfilesystem\fR\fR
759 Creates a new \fBZFS\fR file system. The file system is automatically mounted according to the "mountpoint" property inherited from the parent.
764 \fB\fB-o\fR property=value\fR
768 Sets the specified property as if "\fBzfs set property=value\fR" was invoked at the same time the dataset was created. Any editable \fBZFS\fR property can also be set at creation time. Multiple \fB-o\fR options can be specified. An
769 error results if the same property is specified in multiple \fB-o\fR options.
778 \fB\fBzfs create\fR [\fB-s\fR] [\fB-b\fR \fIblocksize\fR] [[\fB-o\fR property=value]...] \fB-V\fR \fIsize\fR \fIvolume\fR\fR
782 Creates a volume of the given size. The volume is exported as a block device in \fB/dev/zvol/{dsk,rdsk}/\fIpath\fR\fR, where \fIpath\fR is the name of the volume in the \fBZFS\fR namespace. The size represents
783 the logical size as exported by the device. By default, a reservation of equal size is created.
785 \fIsize\fR is automatically rounded up to the nearest 128 Kbytes to ensure that the volume has an integral number of blocks regardless of \fIblocksize\fR.
794 Creates a sparse volume with no reservation. See "volsize" in the Native Properties section for more information about sparse volumes.
801 \fB\fB-o\fR property=value\fR
805 Sets the specified property as if "\fBzfs set property=value\fR" was invoked at the same time the dataset was created. Any editable \fBZFS\fR property can also be set at creation time. Multiple \fB-o\fR options can be specified. An
806 error results if the same property is specified in multiple \fB-o\fR options.
813 \fB\fB-b\fR \fIblocksize\fR\fR
817 Equivalent to "\fB\fR\fB-o\fR \fBvolblocksize=\fIblocksize\fR\fR". If this option is specified in conjunction with "\fB\fR\fB-o\fR \fBvolblocksize\fR", the resulting
818 behavior is undefined.
827 \fB\fBzfs destroy\fR [\fB-rRf\fR] \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR\fR
831 Destroys the given dataset. By default, the command unshares any file systems that are currently shared, unmounts any file systems that are currently mounted, and refuses to destroy a dataset that has active dependents (children, snapshots, clones).
840 Recursively destroy all children. If a snapshot is specified, destroy all snapshots with this name in descendant file systems.
851 Recursively destroy all dependents, including cloned file systems outside the target hierarchy. If a snapshot is specified, destroy all snapshots with this name in descendant file systems.
862 Force an unmount of any file systems using the "\fBunmount -f\fR" command. This option has no effect on non-file systems or unmounted file systems.
865 Extreme care should be taken when applying either the \fB-r\fR or the \fB-f\fR options, as they can destroy large portions of a pool and cause unexpected behavior for mounted file systems in use.
872 \fB\fBzfs clone\fR \fIsnapshot\fR \fIfilesystem\fR|\fIvolume\fR\fR
876 Creates a clone of the given snapshot. See the "Clones" section for details. The target dataset can be located anywhere in the \fBZFS\fR hierarchy, and is created as the same type as the original.
883 \fB\fBzfs promote\fR \fIfilesystem\fR\fR
887 Promotes a clone file system to no longer be dependent on its "origin" snapshot. This makes it possible to destroy the file system that the clone was created from. The clone parent-child dependency relationship is reversed, so that the "origin" file system
888 becomes a clone of the specified file system.
890 The snaphot that was cloned, and any snapshots previous to this snapshot, are now owned by the promoted clone. The space they use moves from the "origin" file system to the promoted clone, so enough space must be available to accommodate these snapshots. No new space is consumed
891 by this operation, but the space accounting is adjusted. The promoted clone must not have any conflicting snapshot names of its own. The "\fBrename\fR" subcommand can be used to rename any conflicting snapshots.
898 \fB\fBzfs rename\fR \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR\fR
902 Renames the given dataset. The new target can be located anywhere in the \fBZFS\fR hierarchy, with the exception of snapshots. Snapshots can only be renamed within the parent file system or volume. When renaming a snapshot, the parent file system of the snapshot does
903 not need to be specified as part of the second argument. Renamed file systems can inherit new mount points, in which case they are unmounted and remounted at the new mount point.
910 \fB\fBzfs snapshot\fR [\fB-r\fR] \fIfilesystem@name\fR|\fIvolume@name\fR\fR
914 Creates a snapshot with the given name. See the "Snapshots" section for details.
923 Recursively create snapshots of all descendant datasets. Snapshots are taken atomically, so that all recursive snapshots correspond to the same moment in time.
932 \fB\fBzfs rollback\fR [\fB-rRf\fR] \fIsnapshot\fR\fR
936 Roll back the given dataset to a previous snapshot. When a dataset is rolled back, all data that has changed since the snapshot is discarded, and the dataset reverts to the state at the time of the snapshot. By default, the command refuses to roll back to a snapshot other than
937 the most recent one. In order to do so, all intermediate snapshots must be destroyed by specifying the \fB-r\fR option. The file system is unmounted and remounted, if necessary.
946 Recursively destroy any snapshots more recent than the one specified.
957 Recursively destroy any more recent snapshots, as well as any clones of those snapshots.
968 Force an unmount of any file systems using the "\fBunmount -f\fR" command.
977 \fB\fBzfs\fR \fBlist\fR [\fB-rH\fR] [\fB-o\fR \fIprop\fR[,\fIprop\fR] ]... [ \fB-t\fR \fItype\fR[,\fItype\fR]...] [ \fB-s\fR \fIprop\fR [\fB-s\fR \fIprop\fR]... [ \fB-S\fR \fIprop\fR [\fB-S\fR \fIprop\fR]... [\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR|\fI/pathname\fR|.\fI/pathname\fR ...\fR
981 Lists the property information for the given datasets in tabular form. If specified, you can list property information by the absolute pathname or the relative pathname. By default, all datasets are displayed and contain the following fields:
985 name,used,available,referenced,mountpoint
998 Used for scripting mode. Do not print headers and separate fields by a single tab instead of arbitrary whitespace.
1009 Recursively display any children of the dataset on the command line.
1016 \fB\fB-o\fR \fIprop\fR\fR
1020 A comma-separated list of properties to display. The property must be one of the properties described in the "Native Properties" section, or the special value "name" to display the dataset name.
1027 \fB\fB-s\fR \fIprop\fR\fR
1031 A property to use for sorting the output by column in ascending order based on the value of the property. The property must be one of the properties described in the "Properties" section, or the special value "name" to sort by the dataset name. Multiple
1032 properties can be specified at one time using multiple \fB-s\fR property options. Multiple \fB-s\fR options are evaluated from left to right in decreasing order of importance.
1034 The following is a list of sorting criteria:
1039 Numeric types sort in numeric order.
1045 String types sort in alphabetical order.
1051 Types inappropriate for a row sort that row to the literal bottom, regardless of the specified ordering.
1057 If no sorting options are specified the existing behavior of "\fBzfs list\fR" is preserved.
1065 \fB\fB-S\fR \fIprop\fR\fR
1069 Same as the \fB-s\fR option, but sorts by property in descending order.
1076 \fB\fB-t\fR \fItype\fR\fR
1080 A comma-separated list of types to display, where "type" is one of "filesystem", "snapshot" or "volume". For example, specifying "\fB-t snapshot\fR" displays only snapshots.
1089 \fB\fBzfs set\fR \fIproperty\fR=\fIvalue\fR \fIfilesystem\fR|\fIvolume\fR ...\fR
1093 Sets the property to the given value for each dataset. Only some properties can be edited. See the "Properties" section for more information on what properties can be set and acceptable values. Numeric values can be specified as exact values, or in a human-readable
1094 form with a suffix of "B", "K", "M", "G", "T", "P", "E", "Z" (for bytes, Kbytes, Mbytes, gigabytes, terabytes, petabytes, exabytes, or zettabytes, respectively). Properties cannot be set on snapshots.
1101 \fB\fBzfs get\fR [\fB-rHp\fR] [\fB-o\fR \fIfield\fR[,\fIfield\fR]...] [\fB-s\fR \fIsource\fR[,\fIsource\fR]...] \fIall\fR | \fIproperty\fR[,\fIproperty\fR]... \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR ...\fR
1105 Displays properties for the given datasets. If no datasets are specified, then the command displays properties for all datasets on the system. For each property, the following columns are displayed:
1110 property Property name
1111 value Property value
1112 source Property source. Can either be local, default,
1113 temporary, inherited, or none (-).
1118 All columns are displayed by default, though this can be controlled by using the \fB-o\fR option. This command takes a comma-separated list of properties as described in the "Native Properties" and "User Properties" sections.
1120 The special value "all" can be used to display all properties for the given dataset.
1129 Recursively display properties for any children.
1140 Display output in a form more easily parsed by scripts. Any headers are omitted, and fields are explicitly separated by a single tab instead of an arbitrary amount of space.
1147 \fB\fB-o\fR \fIfield\fR\fR
1151 A comma-separated list of columns to display. "name,property,value,source" is the default value.
1158 \fB\fB-s\fR \fIsource\fR\fR
1162 A comma-separated list of sources to display. Those properties coming from a source other than those in this list are ignored. Each source must be one of the following: "local,default,inherited,temporary,none". The default value is all sources.
1173 Display numbers in parsable (exact) values.
1182 \fB\fBzfs inherit\fR [\fB-r\fR] \fIproperty\fR \fIfilesystem\fR|\fIvolume\fR ...\fR
1186 Clears the specified property, causing it to be inherited from an ancestor. If no ancestor has the property set, then the default value is used. See the "Properties" section for a listing of default values, and details on which properties can be inherited.
1195 Recursively inherit the given property for all children.
1204 \fB\fBzfs mount\fR\fR
1208 Displays all \fBZFS\fR file systems currently mounted.
1215 \fB\fBzfs mount\fR[\fB-o\fR \fIopts\fR] [\fB-O\fR] \fB-a\fR\fR
1219 Mounts all available \fBZFS\fR file systems. Invoked automatically as part of the boot process.
1224 \fB\fB-o\fR \fIopts\fR\fR
1228 An optional comma-separated list of mount options to use temporarily for the duration of the mount. See the "Temporary Mount Point Properties" section for details.
1239 Perform an overlay mount. See \fBmount\fR(1M) for more information.
1248 \fB\fBzfs mount\fR [\fB-o\fR \fIopts\fR] [\fB-O\fR] \fIfilesystem\fR\fR
1252 Mounts a specific \fBZFS\fR file system. This is typically not necessary, as file systems are automatically mounted when they are created or the mountpoint property has changed. See the "Mount Points" section for details.
1257 \fB\fB-o\fR \fIopts\fR\fR
1261 An optional comma-separated list of mount options to use temporarily for the duration of the mount. See the "Temporary Mount Point Properties" section for details.
1272 Perform an overlay mount. See \fBmount\fR(1M) for more information.
1281 \fB\fBzfs unmount\fR \fB-a\fR\fR
1285 Unmounts all currently mounted \fBZFS\fR file systems. Invoked automatically as part of the shutdown process.
1292 \fB\fBzfs unmount\fR [\fB-f\fR] \fIfilesystem\fR|\fImountpoint\fR\fR
1296 Unmounts the given file system. The command can also be given a path to a \fBZFS\fR file system mount point on the system.
1305 Forcefully unmount the file system, even if it is currently in use.
1314 \fB\fBzfs share\fR \fB-a\fR\fR
1318 Shares all available \fBZFS\fR file systems. This is invoked automatically as part of the boot process.
1325 \fB\fBzfs share\fR \fIfilesystem\fR\fR
1329 Shares a specific \fBZFS\fR file system according to the "sharenfs" property. File systems are shared when the "sharenfs" property is set.
1336 \fB\fBzfs unshare\fR \fB-a\fR\fR
1340 Unshares all currently shared \fBZFS\fR file systems. This is invoked automatically as part of the shutdown process.
1347 \fB\fBzfs unshare\fR [\fB-F\fR] \fIfilesystem\fR|\fImountpoint\fR\fR
1351 Unshares the given file system. The command can also be given a path to a \fBZFS\fR file system shared on the system.
1360 Forcefully unshare the file system, even if it is currently in use.
1369 \fB\fBzfs send\fR [\fB-i\fR \fIsnapshot1\fR] \fIsnapshot2\fR\fR
1373 Creates a stream representation of snapshot2, which is written to standard output. The output can be redirected to a file or to a different system (for example, using \fBssh\fR(1). By default, a full stream is generated.
1378 \fB\fB-i\fR \fIsnapshot1\fR\fR
1382 Generate an incremental stream from \fIsnapshot1\fR to \fIsnapshot2\fR. The incremental source \fIsnapshot1\fR can be specified as the last component of the snapshot name (for example, the part after the "@"),
1383 and it is assumed to be from the same file system as \fIsnapshot2\fR.
1389 The format of the stream is evolving. No backwards compatibility is guaranteed. You may not be able to receive your streams on future versions of \fBZFS\fR.
1394 \fB\fBzfs receive\fR [\fB-vnF\fR] \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR\fR
1398 \fB\fBzfs receive\fR [\fB-vnF\fR] \fB-d\fR \fIfilesystem\fR\fR
1402 Creates a snapshot whose contents are as specified in the stream provided on standard input. If a full stream is received, then a new file system is created as well. Streams are created using the "\fBzfs send\fR" subcommand, which by default creates a full
1403 stream. "\fBzfs recv\fR" can be used as an alias for "\fBzfs receive\fR".
1405 If an incremental stream is received, then the destination file system must already exist, and its most recent snapshot must match the incremental stream's source. The destination file system and all of its child file systems are unmounted and cannot be accessed during the receive operation.
1407 The name of the snapshot (and file system, if a full stream is received) that this subcommand creates depends on the argument type and the \fB-d\fR option.
1409 If the argument is a snapshot name, the specified \fIsnapshot\fR is created. If the argument is a file system or volume name, a snapshot with the same name as the sent snapshot is created within the specified \fIfilesystem\fR or \fIvolume\fR.
1410 If the \fB-d\fR option is specified, the snapshot name is determined by appending the sent snapshot's name to the specified \fIfilesystem\fR. If the \fB-d\fR option is specified, any required file systems within the specified one are created.
1419 Use the name of the sent snapshot to determine the name of the new snapshot as described in the paragraph above.
1430 Print verbose information about the stream and the time required to perform the receive operation.
1441 Do not actually receive the stream. This can be useful in conjunction with the \fB-v\fR option to determine what name the receive operation would use.
1452 Force a rollback of the \fIfilesystem\fR to the most recent snapshot before performing the receive operation.
1461 \fB\fBzfs jail\fR \fIjailid\fR \fIfilesystem\fR\fR
1465 Attaches the given file system to the given jail. From now on this file system tree can be managed from within a jail if the "\fBjailed\fR" property has been set.
1466 To use this functionality, sysctl \fBsecurity.jail.enforce_statfs\fR should be set to 0 and sysctl \fBsecurity.jail.mount_allowed\fR should be set to 1.
1473 \fB\fBzfs unjail\fR \fIjailid\fR \fIfilesystem\fR\fR
1477 Detaches the given file system from the given jail.
1482 \fBExample 1 \fRCreating a ZFS File System Hierarchy
1484 The following commands create a file system named "\fBpool/home\fR" and a file system named "\fBpool/home/bob\fR". The mount point "\fB/export/home\fR" is set for the parent file system, and automatically inherited
1485 by the child file system.
1490 # zfs create pool/home
1491 # zfs set mountpoint=/export/home pool/home
1492 # zfs create pool/home/bob
1498 \fBExample 2 \fRCreating a ZFS Snapshot
1500 The following command creates a snapshot named "yesterday". This snapshot is mounted on demand in the ".zfs/snapshot" directory at the root of the "\fBpool/home/bob\fR" file system.
1505 # zfs snapshot pool/home/bob@yesterday
1511 \fBExample 3 \fRTaking and destroying multiple snapshots
1513 The following command creates snapshots named "\fByesterday\fR" of "\fBpool/home\fR" and all of its descendant file systems. Each snapshot is mounted on demand in the ".zfs/snapshot" directory at the root of its file system. The
1514 second command destroys the newly created snapshots.
1519 # \fBzfs snapshot -r pool/home@yesterday\fR
1520 \fB# zfs destroy -r pool/home@yesterday\fR
1526 \fBExample 4 \fRTurning Off Compression
1528 The following commands turn compression off for all file systems under "\fBpool/home\fR", but explicitly turns it on for "\fBpool/home/anne\fR".
1533 \fB# zfs set compression=off pool/home
1534 # zfs set compression=on pool/home/anne\fR
1540 \fBExample 5 \fRListing ZFS Datasets
1542 The following command lists all active file systems and volumes in the system.
1550 NAME USED AVAIL REFER MOUNTPOINT
1551 pool 100G 60G - /pool
1552 pool/home 100G 60G - /export/home
1553 pool/home/bob 40G 60G 40G /export/home/bob
1554 pool/home/bob@yesterday 3M - 40G -
1555 pool/home/anne 60G 60G 40G /export/home/anne
1561 \fBExample 6 \fRSetting a Quota on a ZFS File System
1563 The following command sets a quota of 50 gbytes for "\fBpool/home/bob\fR".
1568 \fB# zfs set quota=50G pool/home/bob\fR
1574 \fBExample 7 \fRListing ZFS Properties
1576 The following command lists all properties for "\fBpool/home/bob\fR".
1581 \fB# zfs get all pool/home/bob\fR
1584 NAME PROPERTY VALUE SOURCE
1585 pool/home/bob type filesystem -
1586 pool/home/bob creation Fri Feb 23 14:20 2007 -
1587 pool/home/bob used 24.5K -
1588 pool/home/bob available 50.0G -
1589 pool/home/bob referenced 24.5K -
1590 pool/home/bob compressratio 1.00x -
1591 pool/home/bob mounted yes -
1592 pool/home/bob quota 50G local
1593 pool/home/bob reservation none default
1594 pool/home/bob recordsize 128K default
1595 pool/home/bob mountpoint /pool/home/bob default
1596 pool/home/bob sharenfs off default
1597 pool/home/bob shareiscsi off default
1598 pool/home/bob checksum on default
1599 pool/home/bob compression off default
1600 pool/home/bob atime on default
1601 pool/home/bob devices on default
1602 pool/home/bob exec on default
1603 pool/home/bob setuid on default
1604 pool/home/bob readonly off default
1605 pool/home/bob zoned off default
1606 pool/home/bob snapdir hidden default
1607 pool/home/bob aclmode groupmask default
1608 pool/home/bob aclinherit secure default
1609 pool/home/bob canmount on default
1610 pool/home/bob xattr on default
1618 The following command gets a single property value.
1623 \fB# zfs get -H -o value compression pool/home/bob\fR
1630 The following command lists all properties with local settings for "\fBpool/home/bob\fR".
1635 \fB# zfs get -r -s local -o name,property,value all pool/home/bob\fR
1639 pool/home checksum off
1645 \fBExample 8 \fRRolling Back a ZFS File System
1647 The following command reverts the contents of "\fBpool/home/anne\fR" to the snapshot named "\fByesterday\fR", deleting all intermediate snapshots.
1652 \fB# zfs rollback -r pool/home/anne@yesterday\fR
1658 \fBExample 9 \fRCreating a ZFS Clone
1660 The following command creates a writable file system whose initial contents are the same as "\fBpool/home/bob@yesterday\fR".
1665 \fB# zfs clone pool/home/bob@yesterday pool/clone\fR
1671 \fBExample 10 \fRPromoting a ZFS Clone
1673 The following commands illustrate how to test out changes to a file system, and then replace the original file system with the changed one, using clones, clone promotion, and renaming:
1678 \fB# zfs create pool/project/production\fR
1679 populate /pool/project/production with data
1680 \fB# zfs snapshot pool/project/production@today
1681 # zfs clone pool/project/production@today pool/project/beta\fR
1682 make changes to /pool/project/beta and test them
1683 \fB# zfs promote pool/project/beta
1684 # zfs rename pool/project/production pool/project/legacy
1685 # zfs rename pool/project/beta pool/project/production\fR
1686 once the legacy version is no longer needed, it can be
1688 \fB# zfs destroy pool/project/legacy\fR
1694 \fBExample 11 \fRInheriting ZFS Properties
1696 The following command causes "\fBpool/home/bob\fR" and "\fBpool/home/anne\fR" to inherit the "checksum" property from their parent.
1701 \fB# zfs inherit checksum pool/home/bob pool/home/anne\fR
1707 \fBExample 12 \fRRemotely Replicating ZFS Data
1709 The following commands send a full stream and then an incremental stream to a remote machine, restoring them into "\fBpoolB/received/fs\fR@a" and "\fBpoolB/received/fs@b\fR", respectively. "\fBpoolB\fR" must contain
1710 the file system "\fBpoolB/received\fR", and must not initially contain "\fBpoolB/received/fs\fR".
1715 # zfs send pool/fs@a | \e
1716 ssh host zfs receive poolB/received/fs@a
1717 # zfs send -i a pool/fs@b | ssh host \e
1718 zfs receive poolB/received/fs
1724 \fBExample 13 \fRUsing the zfs receive -d Option
1726 The following command sends a full stream of "\fBpoolA/fsA/fsB@snap\fR" to a remote machine, receiving it into "\fBpoolB/received/fsA/fsB@snap\fR". The "\fBfsA/fsB@snap\fR" portion of the received snapshot's name
1727 is determined from the name of the sent snapshot. "\fBpoolB\fR" must contain the file system "\fBpoolB/received\fR". If "\fBpoolB/received/fsA\fR" does not exist, it will be created as an empty file system.
1732 \fB# zfs send poolA/fsA/fsB@snap | \e
1733 ssh host zfs receive -d poolB/received
1740 \fBExample 14 \fRCreating a ZFS volume as a Swap Device
1742 The following example shows how to create a 5-Gbyte ZFS volume and then add the volume as a swap device.
1747 \fB# zfs create -V 5gb tank/vol
1748 # swap -a /dev/zvol/dsk/tank/vol\fR
1754 \fBExample 15 \fRSetting User Properties
1756 The following example sets the user defined "com.example:department" property for a dataset.
1761 \fB# zfs set com.example:department=12345 tank/accounting\fR
1767 \fBExample 16 \fRCreating a ZFS Volume as a iSCSI Target Device
1769 The following example shows how to create a \fBZFS\fR volume as an \fBiSCSI\fR target.
1774 \fB# zfs create -V 2g pool/volumes/vol1
1775 # zfs set shareiscsi=on pool/volumes/vol1
1776 # iscsitadm list target\fR
1777 Target: pool/volumes/vol1
1779 iqn.1986-03.com.sun:02:7b4b02a6-3277-eb1b-e686-a24762c52a8c
1786 After the \fBiSCSI\fR target is created, set up the \fBiSCSI\fR initiator. For more information about the Solaris \fBiSCSI\fR initiator, see the Solaris Administration Guide: Devices and File Systems.
1789 The following exit values are returned:
1798 Successful completion.
1820 Invalid command line options were specified.
1825 See \fBattributes\fR(5) for descriptions of the following attributes:
1831 cw(2.75i) |cw(2.75i)
1832 lw(2.75i) |lw(2.75i)
1834 ATTRIBUTE TYPE
\aATTRIBUTE VALUE
1836 Availability
\aSUNWzfsu
1838 Interface Stability
\aEvolving
1843 \fBgzip\fR(1), \fBssh\fR(1), \fBmount\fR(1M), \fBshare\fR(1M), \fBunshare\fR(1M), \fBzonecfg\fR(1M), \fBzpool\fR(1M), \fBchmod\fR(2), \fBstat\fR(2), \fBfsync\fR(3c), \fBdfstab\fR(4), \fBattributes\fR(5)
projects / FreeBSD / releng / 7.2.git / blob