Property exposes this dependency, and theĬommand lists any such dependencies, if they exist. Original snapshot cannot be destroyed as long as a clone exists. When a snapshot is cloned, it creates an implicit dependency between the parentĮven though the clone is created somewhere else in the dataset hierarchy, the ![]() Since they are very light weight there's littleĪ clone is a writable volume or file system whose initial contents are the sameĪs with snapshots, creating a clone is nearly instantaneous, and initiallyĬlones can only be created from a snapshot. Tied to a snapshot, not the filesystem or volume, and they will survive if the When a snapshot was created as a distinct object. From a storage standpoint a bookmark just provides a way to reference Unlike snapshots, bookmarks can not be accessed through the filesystem in any Snapshots are automatically mounted on demand and may be unmounted at regularĪ bookmark is like a snapshot, a read-only copy of a file system or volume.īookmarks can be created extremely quickly, compared to snapshots, and theyĬonsume no additional space within the pool. Snapshots of volumes can be cloned or rolled back, visibility is determinedįile system snapshots can be accessed under theĭirectory in the root of the file system. Would otherwise be shared with the active dataset. Snapshots can be created extremely quickly, and initially consume no additionalĪs data within the active dataset changes, the snapshot consumes more data than The physical storage characteristics, however, are managed by theįor more information on creating and administering pools.Ī snapshot is a read-only copy of a file system or volume. Unmounting, taking snapshots, and setting properties. The root of the pool can be accessed as a file system, such as mounting and It is specified asĪ ZFS storage pool is a logical collection of devices that provide space forĪ storage pool is also the root of the ZFS file system hierarchy. This type of dataset should only be used when a block device is required.įile systems are typically used in most environments.Ī read-only version of a file system or volume at a given point in time.īut without the hold on on-disk data. While ZFS file systems are designed to be POSIX compliant, known issues existĪpplications that depend on standards conformance might fail due to non-standardīehavior when checking file system free space.Ī logical volume exported as a raw or block device. Where the maximum length of a dataset name isĪnd the maximum amount of nesting allowed in a path is 50 levels deep.Ĭan be mounted within the standard system namespace and behaves like other file Ĭommand configures ZFS datasets within a ZFS storage pool, as described inĪ dataset is identified by a unique path within the ZFS namespace. s setname perm | setname [, perm | setname. e | everyone perm | setname [, perm | setname. ![]() ![]() [ filesystem | volume | snapshot | bookmark. įilesystem | volume | snapshot filesystem | volume | snapshot Index NAME SYNOPSIS DESCRIPTION ZFS File System Hierarchy Snapshots Bookmarks Clones Mount Points Deduplication Native Properties Temporary Mount Point Properties User Properties ZFS Volumes as Swap Encryption SUBCOMMANDS EXIT STATUS EXAMPLES INTERFACE STABILITY SEE ALSOįilesystem | volume snap [% snap [, snap [% snap.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |