neulab/tldr huggingface dataset:
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.
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.
Native Properties Properties are divided into two types, native properties and user defined properties. Native properties either export internal statistics or control ZFS behavior. In addition, native properties are either editable or read-only. User properties have no effect on ZFS behavior, 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.
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 that are not applicable to snapshots are not displayed.
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:
"1536M", "1.5g", "1.50GB".
The values of non-numeric properties are case sensitive and must be lowercase, except for "mountpoint" and "sharenfs".
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.
type             The type of dataset: "filesystem", "volume", "snapshot", or "clone".
creation         The time this dataset was created.
used             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.  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.
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 the snapshot's space used. Additionally, deleting snapshots can increase the amount of space unique to (and used by) other snapshots.
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 fsync(3c) or O_SYNC does not necessarily guarantee that the space usage information is updated immediately.
available        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 within the pool.
This property can also be referred to by its shortened column name, "avail".
referenced       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 identical.
This property can also be referred to by its shortened column name, "refer".
compressratio    The compression ratio achieved for this dataset, expressed as a multiplier. Compression can be turned on by running "zfs set compression=on dataset". The default value is "off".
mounted          For file systems, indicates whether the file system is currently mounted. This property can be either "yes" or "no".
origin           For cloned file systems or volumes, the snapshot from which the clone was created. The origin cannot be destroyed (even with the -r or -f options) so long as a clone exists.
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.
quota=size | none
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 has a quota does not override the ancestor's quota, but rather imposes an additional limit.
Quotas cannot be set on volumes, as the "volsize" property acts as an implicit quota.
reservation=size | none
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 used, and count against the parent datasets' quotas and reservations.
This property can also be referred to by its shortened column name, "reserv".
volsize=size
For volumes, specifies the logical size of the volume. By default, creating a volume establishes a reservation of equal size. Any changes to volsize are reflected in an equivalent change to the reservation. The volsize can only be set to a multiple of volblocksize, and cannot be zero.
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 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.
Though not recommended, a "sparse volume" (also known as "thin provisioning") can be created by specifying the -s option to the "zfs create -V" command, or by changing the reservation after the volume has been created.  A "sparse volume" is a volume where the reservation is less then the volume size. Consequently, writes to a sparse volume can fail with ENOSPC when the pool is low on space. For a sparse volume, changes to volsize are not reflected in the reservation.
volblocksize=blocksize
For volumes, specifies the block size of the volume. The blocksize cannot be changed once the volume has been written, so it should be set at volume creation time. The default blocksize for volumes is 8 Kbytes. Any power of 2 from 512 bytes to 128 Kbytes is valid.
This property can also be referred to by its shortened column name, "volblock".
recordsize=size
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. ZFS automatically tunes block sizes according to internal algorithms optimized for typical access patterns.
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 purpose file systems is strongly discouraged, and may adversely affect performance.
The size specified must be a power of two greater than or equal to 512 and less than or equal to 128 Kbytes.
Changing the file system's recordsize only affects files created afterward; existing files are unaffected.
This property can also be referred to by its shortened column name, "recsize".
mountpoint=path | none | legacy
Controls the mount point used for this file system. See the "Mount Points" section for more information on how this property is used.
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 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.
sharenfs=on | off | opts
Controls whether the file system is shared via NFS, and what options are used. A file system with a sharenfs property of "off" is managed through traditional tools such as share(1M), unshare(1M), and dfstab(4). Otherwise, the file system is automatically shared and unshared with the "zfs share" and "zfs unshare" commands. If the property is set to "on", the share(1M) command is invoked with no options. Otherwise, the share(1M) command is invoked with options equivalent to the contents of this property.
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", the file systems are unshared.
shareiscsi=on | off
Like the "sharenfs" property, "shareiscsi" indicates whether a ZFS volume is exported as an iSCSI target. The acceptable values for this property are "on", "off", and "type=disk".  The default value is "off". In the future, other target types might be supported. For example, "tape".
You might want to set "shareiscsi=on" for a file system so that all ZFS volumes within the file system are shared by default. Setting this property on a file system has no direct effect, however.
checksum=on | off | fletcher2, | fletcher4 | sha256
Controls the checksum used to verify data integrity. The default value is "on", which automatically selects an appropriate algorithm (currently, fletcher2, but this may change in future releases). The value "off" disables integrity checking on user data. Disabling checksums is NOT a recommended practice.
compression=on | off | lzjb | gzip | gzip-N
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" compression algorithm uses the same compression as the gzip(1) command.  You can specify the "gzip" level by using the value "gzip-N", where N is an integer from 1 (fastest) to 9 (best compression ratio). Currently, "gzip" is equivalent to "gzip-6" (which is also the default for gzip(1)).
This property can also be referred to by its shortened column name "compress".
atime=on | off
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 is "on".
devices=on | off
Controls whether device nodes can be opened on this file system. The default value is "on".
exec=on | off
Controls whether processes can be executed from within this file system. The default value is "on".
setuid=on | off
Controls whether the set-UID bit is respected for the file system. The default value is "on".
readonly=on | off
Controls whether this dataset can be modified. The default value is "off".
This property can also be referred to by its shortened column name, "rdonly".
zoned=on | off
Controls whether the dataset is managed from a non-global zone. See the "Zones" section for more information. The default value is "off".
snapdir=hidden | visible
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".
aclmode=discard | groupmask | passthrough
Controls how an ACL is modified during chmod(2). A file system with an "aclmode" property of "discard" deletes all ACL entries that do not represent the mode of the file. An "aclmode" property of "groupmask" (the default) reduces user or group permissions. The permissions are reduced, such that they are no greater than the group permission bits, unless it is a user entry that has the same UID as the owner of the file or directory. In this case, the ACL permissions are reduced so that they are no greater than owner permission bits. A file system with an "aclmode" property of "passthrough" indicates that no changes will be made to the ACL other than generating the necessary ACL entries to represent the new mode of the file or directory.
aclinherit=discard | noallow | secure | passthrough
Controls how ACL entries are inherited when files and directories are created. A file system with an "aclinherit" property of "discard" does not inherit any ACL entries. A file system with an "aclinherit" property value of "noallow" only inherits inheritable ACL entries that specify "deny" permissions. The property value "secure" (the default) removes the "write_acl" and "write_owner" permissions when the ACL entry is inherited. A file system with an "aclinherit" property value of "passthrough" inherits all inheritable ACL entries without any modifications made to the ACL entries when they are inherited.
canmount=on | off
If this property is set to "off", the file system cannot be mounted, and is ignored by "zfs mount -a". This is similar to setting the "mountpoint" property to "none", except 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 in the same directory, but may have different inherited characteristics. The default value is "on".
This property is not inherited.
xattr=on | off
Controls whether extended attributes are enabled for this file system. The default value is "on".
copies=1 | 2 | 3
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 file and dataset, changing the "used" property and counting against quotas and reservations.
Changing this property only affects newly-written data. Therefore, set this property at file system creation time by using the "-o copies=" option.
iscsioptions This read-only property, which is hidden, is used by the iSCSI target daemon to store persistent information, such as the IQN. It cannot be viewed or modified using the zfs command. The contents are not intended for external consumers.
Temporary Mount Point Properties When a file system is mounted, either through mount(1M) for legacy mounts or the "zfs mount" command for normal file systems, its mount options are set according to its properties. The correlation between properties and mount options is as follows:
PROPERTY                MOUNT OPTION devices                 devices/nodevices exec                    exec/noexec readonly                ro/rw setuid                  setuid/nosetuid xattr                   xattr/noxattr
In addition, these options can be set on a per-mount basis using the -o 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 -nosuid option is an alias for "nodevices,nosetuid".  These properties are reported as "temporary" by the "zfs get" command. If the properties are changed while the dataset is mounted, the new setting overrides any temporary settings.
User Properties In addition to the standard native properties, ZFS supports arbitrary user properties. User properties have no effect on ZFS behavior, but applications or administrators can use them to annotate datasets.
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 ("_"). The expected convention is that the property name is divided into two portions such as "module:property", but this namespace is not enforced by ZFS. User property names can be at most 256 characters, and cannot begin with a dash ("-").
When making programmatic use of user properties, it is strongly suggested to use a reversed DNS domain name for the module component of property names to reduce the chance that two independently-developed packages use the same property name for different purposes. Property names beginning with "com.sun." are reserved for use by Sun Microsystems.
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.  Use the "zfs inherit" 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.
Volumes as Swap or Dump Devices To set up a swap area, create a ZFS volume of a specific size and then enable swap on that device. For more information, see the EXAMPLES section.
Do not swap to a file on a ZFS file system. A ZFS swap file configuration is not supported.
Using a ZFS volume as a dump device is not supported.
All subcommands that modify state are logged persistently to the pool in their original form.
zfs ?
Displays a help message.
zfs create [[-o property=value]...] filesystem
Creates a new ZFS file system. The file system is automatically mounted according to the "mountpoint" property inherited from the parent.
-o property=value    Sets the specified property as if "zfs set property=value" was invoked at the same time the dataset was created. Any editable ZFS property can also be set at creation time. Multiple -o options can be specified. An error results if the same property is specified in multiple -o options.
zfs create [-s] [-b blocksize] [[-o property=value]...] -V size volume
Creates a volume of the given size. The volume is exported as a block device in /dev/zvol/{dsk,rdsk}/path, where path is the name of the volume in the ZFS namespace. The size represents the logical size as exported by the device. By default, a reservation of equal size is created.
size is automatically rounded up to the nearest 128 Kbytes to ensure that the volume has an integral number of blocks regardless of blocksize.
-s                   Creates a sparse volume with no reservation. See "volsize" in the Native Properties section for more information about sparse volumes.
-b blocksize         Equivalent to "-o volblocksize=blocksize". If this option is specified in conjunction with "-o volblocksize", the resulting behavior is undefined.
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).
-r    Recursively destroy all children. If a snapshot is specified, destroy all snapshots with this name in descendant file systems.
-R    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.
-f    Force an unmount of any file systems using the "unmount -f" command. This option has no effect on non-file systems or unmounted file systems.
Extreme care should be taken when applying either the -r or the -f options, as they can destroy large portions of a pool and cause unexpected behavior for mounted file systems in use.
Creates a clone of the given snapshot. See the "Clones" section for details. The target dataset can be located anywhere in the ZFS hierarchy, and is created as the same type as the original.
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 becomes a clone of the specified file system.
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 by this operation, but the space accounting is adjusted. The promoted clone must not have any conflicting snapshot names of its own. The "rename" subcommand can be used to rename any conflicting snapshots.
zfs rename filesystem|volume|snapshot filesystem|volume|snapshot
Renames the given dataset. The new target can be located anywhere in the ZFS 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 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.
Creates a snapshot with the given name. See the "Snapshots" section for details.
-r    Recursively create snapshots of all descendant datasets. Snapshots are taken atomically, so that all recursive snapshots correspond to the same moment in time.
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 the most recent one. In order to do so, all intermediate snapshots must be destroyed by specifying the -r option. The file system is unmounted and remounted, if necessary.
-r    Recursively destroy any snapshots more recent than the one specified.
-R    Recursively destroy any more recent snapshots, as well as any clones of those snapshots.
-f    Force an unmount of any file systems using the "unmount -f" command.
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:
name,used,available,referenced,mountpoint
-H         Used for scripting mode. Do not print headers and separate fields by a single tab instead of arbitrary whitespace.
-r         Recursively display any children of the dataset on the command line.
-o prop    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.
-s prop    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 properties can be specified at one time using multiple -s property options. Multiple -s options are evaluated from left to right in decreasing order of importance.
The following is a list of sorting criteria:
o      Numeric types sort in numeric order.
o      String types sort in alphabetical order.
o      Types inappropriate for a row sort that row to the literal bottom, regardless of the specified ordering.
o      If no sorting options are specified the existing behavior of "zfs list" is preserved.
-S prop    Same as the -s option, but sorts by property in descending order.
-t type    A comma-separated list of types to display, where "type" is one of "filesystem", "snapshot" or "volume". For example, specifying "-t snapshot" displays only snapshots.
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 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.
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:
name      Dataset name property  Property name value     Property value source    Property source. Can either be local, default, temporary, inherited, or none (-).
All columns are displayed by default, though this can be controlled by using the -o option. This command takes a comma-separated list of properties as described in the "Native Properties" and "User Properties" sections.
The special value "all" can be used to display all properties for the given dataset.
-r           Recursively display properties for any children.
-H           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.
-o field     A comma-separated list of columns to display. "name,property,value,source" is the default value.
-s source    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.
-p           Display numbers in parsable (exact) values.
zfs inherit [-r] property filesystem|volume ...
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.
-r    Recursively inherit the given property for all children.
Displays all ZFS file systems currently mounted.
zfs mount[-o opts] [-O] -a
Mounts all available ZFS file systems. Invoked automatically as part of the boot process.
-o opts    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.
-O         Perform an overlay mount. See mount(1M) for more information.
zfs mount [-o opts] [-O] filesystem
Mounts a specific ZFS 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.
zfs unmount -a
Unmounts all currently mounted ZFS file systems. Invoked automatically as part of the shutdown process.
Unmounts the given file system. The command can also be given a path to a ZFS file system mount point on the system.
-f    Forcefully unmount the file system, even if it is currently in use.
Shares all available ZFS file systems. This is invoked automatically as part of the boot process.
Shares a specific ZFS file system according to the "sharenfs" property. File systems are shared when the "sharenfs" property is set.
zfs unshare -a
Unshares all currently shared ZFS file systems. This is invoked automatically as part of the shutdown process.
zfs unshare [-F] filesystem|mountpoint
Unshares the given file system. The command can also be given a path to a ZFS file system shared on the system.
-F    Forcefully unshare the file system, even if it is currently in use.
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 ssh(1). By default, a full stream is generated.
-i snapshot1    Generate an incremental stream from snapshot1 to snapshot2. The incremental source snapshot1 can be specified as the last component of the snapshot name (for example, the part after the "@"), and it is assumed to be from the same file system as snapshot2.
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 ZFS.
zfs receive [-vnF] filesystem|volume|snapshot zfs receive [-vnF] -d filesystem
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 "zfs send" subcommand, which by default creates a full stream. "zfs recv" can be used as an alias for "zfs receive".
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.
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 -d option.
If the argument is a snapshot name, the specified snapshot 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 filesystem or volume.  If the -d option is specified, the snapshot name is determined by appending the sent snapshot's name to the specified filesystem. If the -d option is specified, any required file systems within the specified one are created.
-d    Use the name of the sent snapshot to determine the name of the new snapshot as described in the paragraph above.
-v    Print verbose information about the stream and the time required to perform the receive operation.
-n    Do not actually receive the stream. This can be useful in conjunction with the -v option to determine what name the receive operation would use.
-F    Force a rollback of the filesystem to the most recent snapshot before performing the receive operation.
Example 1 Creating a ZFS File System Hierarchy
The following commands create a file system named "pool/home" and a file system named "pool/home/bob". The mount point "/export/home" is set for the parent file system, and automatically inherited by the child file system.
# zfs create pool/home # zfs set mountpoint=/export/home pool/home # zfs create pool/home/bob
Example 2 Creating a ZFS Snapshot
The following command creates a snapshot named "yesterday". This snapshot is mounted on demand in the ".zfs/snapshot" directory at the root of the "pool/home/bob" file system.
# zfs snapshot pool/home/bob@yesterday
Example 3 Taking and destroying multiple snapshots
The following command creates snapshots named "yesterday" of "pool/home" 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 second command destroys the newly created snapshots.
# zfs snapshot -r pool/home@yesterday # zfs destroy -r pool/home@yesterday
Example 4 Turning Off Compression
The following commands turn compression off for all file systems under "pool/home", but explicitly turns it on for "pool/home/anne".
# zfs set compression=off pool/home # zfs set compression=on pool/home/anne
Example 5 Listing ZFS Datasets
The following command lists all active file systems and volumes in the system.
# zfs list
NAME                      USED  AVAIL  REFER  MOUNTPOINT pool                      100G   60G       -  /pool pool/home                 100G   60G       -  /export/home pool/home/bob              40G   60G     40G  /export/home/bob pool/home/bob@yesterday     3M     -     40G  - pool/home/anne             60G   60G     40G  /export/home/anne
Example 6 Setting a Quota on a ZFS File System
The following command sets a quota of 50 gbytes for "pool/home/bob".
# zfs set quota=50G pool/home/bob
Example 7 Listing ZFS Properties
The following command lists all properties for "pool/home/bob".
# zfs get all pool/home/bob
NAME           PROPERTY       VALUE                  SOURCE pool/home/bob  type           filesystem             - pool/home/bob  creation       Fri Feb 23 14:20 2007  - pool/home/bob  used           24.5K                  - pool/home/bob  available      50.0G                  - pool/home/bob  referenced     24.5K                  - pool/home/bob  compressratio  1.00x                  - pool/home/bob  mounted        yes                    - pool/home/bob  quota          50G                    local pool/home/bob  reservation    none                   default pool/home/bob  recordsize     128K                   default pool/home/bob  mountpoint     /pool/home/bob         default pool/home/bob  sharenfs       off                    default pool/home/bob  shareiscsi     off                    default pool/home/bob  checksum       on                     default pool/home/bob  compression    off                    default pool/home/bob  atime          on                     default pool/home/bob  devices        on                     default pool/home/bob  exec           on                     default pool/home/bob  setuid         on                     default pool/home/bob  readonly       off                    default pool/home/bob  zoned          off                    default pool/home/bob  snapdir        hidden                 default pool/home/bob  aclmode        groupmask              default pool/home/bob  aclinherit     secure                 default pool/home/bob  canmount       on                     default pool/home/bob  xattr          on                     default
The following command gets a single property value.
# zfs get -H -o value compression pool/home/bob on
The following command lists all properties with local settings for "pool/home/bob".
# zfs get -r -s local -o name,property,value all pool/home/bob
NAME             PROPERTY      VALUE pool             compression   on pool/home        checksum      off
Example 8 Rolling Back a ZFS File System
The following command reverts the contents of "pool/home/anne" to the snapshot named "yesterday", deleting all intermediate snapshots.
# zfs rollback -r pool/home/anne@yesterday
Example 9 Creating a ZFS Clone
The following command creates a writable file system whose initial contents are the same as "pool/home/bob@yesterday".
# zfs clone pool/home/bob@yesterday pool/clone
Example 10 Promoting a ZFS Clone
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:
# zfs create pool/project/production populate /pool/project/production with data # zfs snapshot pool/project/production@today # zfs clone pool/project/production@today pool/project/beta make changes to /pool/project/beta and test them # zfs promote pool/project/beta # zfs rename pool/project/production pool/project/legacy # zfs rename pool/project/beta pool/project/production once the legacy version is no longer needed, it can be destroyed # zfs destroy pool/project/legacy
Example 11 Inheriting ZFS Properties
The following command causes "pool/home/bob" and "pool/home/anne" to inherit the "checksum" property from their parent.
# zfs inherit checksum pool/home/bob pool/home/anne
Example 12 Remotely Replicating ZFS Data
The following commands send a full stream and then an incremental stream to a remote machine, restoring them into "poolB/received/fs@a" and "poolB/received/fs@b", respectively. "poolB" must contain the file system "poolB/received", and must not initially contain "poolB/received/fs".
# zfs send pool/fs@a | \ ssh host zfs receive poolB/received/fs@a # zfs send -i a pool/fs@b | ssh host \ zfs receive poolB/received/fs
Example 13 Using the  zfs receive -d Option
The following command sends a full stream of "poolA/fsA/fsB@snap" to a remote machine, receiving it into "poolB/received/fsA/fsB@snap". The "fsA/fsB@snap" portion of the received snapshot's name is determined from the name of the sent snapshot. "poolB" must contain the file system "poolB/received".  If  "poolB/received/fsA" does not exist, it will be created as an empty file system.
# zfs send poolA/fsA/fsB@snap | \ ssh host zfs receive -d poolB/received
Example 14 Creating a ZFS volume as a Swap Device
The following example shows how to create a 5-Gbyte ZFS volume and then add the volume as a swap device.
# zfs create  -V 5gb tank/vol # swap -a /dev/zvol/dsk/tank/vol
Example 15 Setting User Properties
The following example sets the user defined "com.example:department" property for a dataset.
# zfs set com.example:department=12345 tank/accounting
Example 16 Creating a ZFS Volume as a iSCSI Target Device
The following example shows how to create a ZFS volume as an iSCSI target.
# zfs create -V 2g pool/volumes/vol1 # zfs set shareiscsi=on pool/volumes/vol1 # iscsitadm list target Target: pool/volumes/vol1 iSCSI Name: iqn.1986-03.com.sun:02:7b4b02a6-3277-eb1b-e686-a24762c52a8c Connections: 0
After the iSCSI target is created, set up the iSCSI initiator. For more information about the Solaris iSCSI initiator, see the Solaris Administration Guide: Devices and File Systems.
1    An error occurred.
2    Invalid command line options were specified.
See attributes(5) for descriptions of the following attributes:
┌─────────────────────────────┬─────────────────────────────┐ │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │ ├─────────────────────────────┼─────────────────────────────┤ │Availability                 │SUNWzfsu                     │ ├─────────────────────────────┼─────────────────────────────┤ │Interface Stability          │Evolving                     │ └─────────────────────────────┴─────────────────────────────┘
gzip(1), ssh(1), mount(1M), share(1M), unshare(1M), zonecfg(1M), zpool(1M), chmod(2), stat(2), fsync(3c), dfstab(4), attributes(5)
MOSQUITTO_PUB(1)                    Commands                    MOSQUITTO_PUB(1)
mosquitto_pub - an MQTT version 5/3.1.1/3.1 client for publishing simple messages
mosquitto_pub {[-h hostname] [--unix socket path] [-p port-number] [-u username] [-P password] -t message-topic... | -L URL} [-A bind-address] [-c] [-d] [-D command identifier value] [-i client-id] [-I client-id-prefix] [-k keepalive-time] [--nodelay] [-q message-QoS] [--quiet] [-r] [--repeat count] [--repeat-delay seconds] [-S] [-V protocol-version] [-x session-expiry-interval] {-f file | -l | -m message | -n | -s} [--will-topic topic [--will-payload payload] [--will-qos qos] [--will-retain]] [[{--cafile file | --capath dir} [--cert file] [--key file] [--ciphers ciphers] [--tls-version version] [--tls-alpn protocol] [--tls-engine engine] [--keyform {pem | engine}] [--tls-engine-kpass-sha1 kpass-sha1] [--tls-use-os-certs] [--insecure]] | [--psk hex-key --psk-identity identity [--ciphers ciphers] [--tls-version version]]] [--proxy socks-url]
mosquitto_pub [--help]
mosquitto_pub is a simple MQTT version 5/3.1.1 client that will publish a single message on a topic and exit.
mosquitto_pub supports TLS encrypted connections. It is strongly recommended that you use an encrypted connection for anything more than the most basic setup.
The options below may be given on the command line, but may also be placed in a config file located at $XDG_CONFIG_HOME/mosquitto_pub or $HOME/.config/mosquitto_pub with one pair of -option value per line. The values in the config file will be used as defaults and can be overridden by using the command line. The exceptions to this are the message type options, of which only one can be specified. Note also that currently some options cannot be negated, e.g.  -S. Config file lines that have a # as the first character are treated as comments and not processed any further.
command is the MQTT command/packet identifier and can be one of CONNECT, PUBLISH, PUBREL, DISCONNECT, AUTH, or WILL. The properties available for each command are listed in the Properties section.
-f, --file Send the contents of a file as the message.
-l, --stdin-line Send messages read from stdin, splitting separate lines into separate messages.
-m, --message Send a single message from the command line.
-n, --null-message Send a null (zero length) message.
-q, --qos Specify the quality of service to use for the message, from 0, 1 and 2. Defaults to 0.
-r, --retain If retain is given, the message will be retained as a "last known good" value on the broker. See mqtt(7) for more information. Note that zero length payloads are never retained. If you send a zero length payload retained message it will clear any retained message on the topic.
--repeat If the publish mode is-m, -f, or -s (i.e. the modes where only a single message is sent), then --repeat can be used to specify that the message will be published multiple times.
See also --repeat-delay.
--repeat-delay If using --repeat, then the default behaviour is to publish repeated messages as soon as the previous message is delivered. Use --repeat-delay to specify the number of seconds to wait after the previous message was delivered before publishing the next. Does not need to be an integer number of seconds.
Note that there is no guarantee as to the actual interval between messages, this option simply defines the minimum time from delivery of one message to the start of the publish of the next.
-s, --stdin-file Send a message read from stdin, sending the entire content as a single message.
-t, --topic The MQTT topic on which to publish the message. See mqtt(7) for more information on MQTT topics.
-V, --protocol-version Specify which version of the MQTT protocol should be used when connecting to the rmeote broker. Can be 5, 311, 31, or the more verbose mqttv5, mqttv311, or mqttv31. Defaults to 311.
--will-retain If given, if the client disconnects unexpectedly the message sent out will be treated as a retained message. This must be used in conjunction with --will-topic. Note that zero length payloads are never retained. If you send a zero length payload retained message it will clear any retained message on the topic.
The -D / --property option allows adding properties to different stages of the mosquitto_pub run. The properties supported for each command are as follows:
Connect •   authentication-data (binary data - note treated as a string in mosquitto_pub)
•   authentication-method (UTF-8 string pair)
Publish •   content-type (UTF-8 string)
•   correlation-data (binary data - note treated as a string in mosquitto_pub)
•   topic-alias (16-bit unsigned integer)
Publish temperature information to localhost with QoS 1:
•   mosquitto_pub -t sensors/temperature -m 32 -q 1
Publish timestamp and temperature information to a remote host on a non-standard port and QoS 0:
•   mosquitto_pub -h 192.168.1.1 -p 1885 -t sensors/temperature -m "1266193804 32"
Publish light switch status. Message is set to retained because there may be a long period of time between light switch events:
•   mosquitto_pub -r -t switches/kitchen_lights/status -m "on"
Send the contents of a file in two ways:
•   mosquitto_pub -t my/topic -f ./data
•   mosquitto_pub -t my/topic -s < ./data
Send parsed electricity usage data from a Current Cost meter, reading from stdin with one line/reading as one message:
•   read_cc128.pl | mosquitto_pub -t sensors/cc128 -l
$XDG_CONFIG_HOME/mosquitto_pub, $HOME/.config/mosquitto_pub Configuration file for default options.
mqtt(7), mosquitto_rr(1), mosquitto_sub(1), mosquitto(8), libmosquitto(3), mosquitto-tls(7)
pdfjam(1)                                                              pdfjam(1)
pdfjam - A shell script for manipulating PDF files
pdfjam [OPTION [OPTION] ...] [SRC [PAGESPEC] [SRC [PAGESPEC]] ...]
pdfjam provides a front end to most capabilities of the "pdfpages" package (by Andreas Matthias) of pdflatex.  Detailed information can be found via "pdfjam --help", and also in the web page mentioned below .
A working installation of pdflatex, with the pdfpages package, is required.
The pdfjam script is distributed as (the main) part of the PDFjam package.  The homepage of PDFjam is at http://go.warwick.ac.uk/pdfjam .
Configuration of the PDFjam utilities involves specifying the location of pdflatex, the location of temporary files, specification of default page size, etc.  This is done in a block of lines near the top of the pdfjam script; settings made there are over-ridden by any that are found at a site-wide configuration file (at /etc/pdfjam.conf, /usr/share/etc/pdfjam.conf, /usr/local/share/pdfjam.conf, or /usr/local/etc/pdfjam.conf), which in turn are over-ridden by any that are found in a user-defaults file at ~/.pdfjam.conf.
pdfjam does not work with encrypted PDF files, and does not preserve hyperlinks.
Please report bugs! See the website at http://go.warwick.ac.uk/pdfjam .
The PDFjam package is written and maintained by David Firth.
ANSIBLE-GALAXY(1)        System administration commands        ANSIBLE-GALAXY(1)
ansible-galaxy - Perform various Role and Collection related operations.
usage: ansible-galaxy [-h] [--version] [-v] TYPE ...
command to manage Ansible roles in shared repositories, the default of which is Ansible Galaxy https://galaxy.ansible.com.
collection Perform the action on an Ansible Galaxy collection. Must be combined with a further action like init/install as listed below.
role   Perform the action on an Ansible Galaxy role. Must be combined with a further action like delete/install/init as listed below.
ansible (1), ansible-config (1), ansible-console (1), ansible-doc (1), ansible-inventory (1), ansible-playbook (1), ansible-pull (1), ansible-vault (1)
FC-LIST(1)                                                            FC-LIST(1)
fc-list - list available fonts
fc-list [ -vVh ] [ --verbose ] [ -f format | --format format ] [ -q | --quiet ] [ --version ] [ --help ] [ pattern  [ element ... ]  ]
fc-list lists fonts and styles available on the system for applications using fontconfig.  If any elements are specified, only those are printed. Otherwise family and style are printed, unless verbose output is requested.
-q --quiet Suppress all normal output. returns 1 as the error code if no fonts matched.
pattern If this argument is set, only fonts matching pattern are displayed.
fc-list Lists all font faces.
fc-list :lang=hi Lists font faces that cover Hindi.
fc-list : family style file spacing Lists the filename and spacing value for each font face.  ``:'' is an empty pattern that matches all fonts.
fc-match(1) FcFontList(3) FcPatternFormat(3) fc-cat(1) fc-cache(1) fc- pattern(1) fc-query(1) fc-scan(1)
GIT-COLUMN(1)                      Git Manual                      GIT-COLUMN(1)
git-column - Display data in columns
git column [--command=<name>] [--[raw-]mode=<mode>] [--width=<width>] [--indent=<string>] [--nl=<string>] [--padding=<n>]
This command formats the lines of its standard input into a table with multiple columns. Each input line occupies one cell of the table. It is used internally by other git commands to format output into columns.
--command=<name> Look up layout mode using configuration variable column.<name> and column.ui.
--mode=<mode> Specify layout mode. See configuration variable column.ui for option syntax in git-config(1).
--raw-mode=<n> Same as --mode but take mode encoded as a number. This is mainly used by other commands that have already parsed layout mode.
--width=<width> Specify the terminal width. By default git column will detect the terminal width, or fall back to 80 if it is unable to do so.
--indent=<string> String to be printed at the beginning of each line.
--nl=<string> String to be printed at the end of each line, including newline character.
--padding=<N> The number of spaces between columns. One space by default.
Format data by columns:
$ seq 1 24 | git column --mode=column --padding=5 1      4      7      10     13     16     19     22 2      5      8      11     14     17     20     23 3      6      9      12     15     18     21     24
Format data by rows:
$ seq 1 21 | git column --mode=row --padding=5 1      2      3      4      5      6      7 8      9      10     11     12     13     14 15     16     17     18     19     20     21
List some tags in a table with unequal column widths:
$ git tag --list 'v2.4.*' --column=row,dense v2.4.0  v2.4.0-rc0  v2.4.0-rc1  v2.4.0-rc2  v2.4.0-rc3 v2.4.1  v2.4.10     v2.4.11     v2.4.12     v2.4.2 v2.4.3  v2.4.4      v2.4.5      v2.4.6      v2.4.7 v2.4.8  v2.4.9