|ZPOOL-CREATE(8)||System Manager's Manual||ZPOOL-CREATE(8)|
Creates a new ZFS storage pool
] pool vdev...
-ocompatibility=off | legacy | file [,file...]]... [
-Rroot] pool vdev...
- Creates a new storage pool containing the virtual devices specified on the
command line. The pool name must begin with a letter, and can only contain
alphanumeric characters as well as underscore
(“ ”), and period
(“.”). The pool names
draid, spare and
log are reserved, as are names beginning with
and the pattern c[0-9]. The
vdev specification is described in the
Virtual Devices section of
The command attempts to verify that each device specified is accessible and
not currently in use by another subsystem. However this check is not
robust enough to detect simultaneous attempts to use a new device in
different pools, even if multihost is
enabled. The administrator must ensure that
simultaneous invocations of any combination of
zpool replace, zpool
create, zpool add, or
zpool labelclear, do not refer to the same
device. Using the same device in two pools will result in pool corruption.
There are some uses, such as being currently mounted, or specified as the
dedicated dump device, that prevents a device from ever being used by ZFS.
Other uses, such as having a preexisting UFS file system, can be
overridden with the
-foption. The command also checks that the replication strategy for the pool is consistent. An attempt to combine redundant and non-redundant storage in a single pool, or to mix disks and files, results in an error unless
-fis specified. The use of differently sized devices within a single raidz or mirror group is also flagged as an error unless
-fis specified. Unless the
-Roption is specified, the default mount point is /pool. The mount point must not exist or must be empty, or else the root dataset cannot be mounted. This can be overridden with the
-moption. By default all supported features are enabled on the new pool. The
-doption or the
-ocompatibility property (eg:
-ocompatibility=2020 ) can be used to restrict the features that are enabled, so that the pool can be imported on other releases of the ZFS software.
- Do not enable any features on the new pool. Individual features can be
enabled by setting their corresponding properties to
enabled with the
-ooption. See zpool-features(5) for details about feature properties.
- Forces use of vdevs, even if they appear in use or specify a conflicting replication level. Not all devices can be overridden in this manner.
- Sets the mount point for the root dataset. The default mount point is /pool or altroot/pool if altroot is specified. The mount point must be an absolute path, legacy, or none. For more information on dataset mount points, see zfs(8).
- Displays the configuration that would be used without actually creating the pool. The actual pool creation can still fail due to insufficient privileges or device sharing.
- Sets the given pool properties. See the zpoolprops manual page for a list of valid properties that can be set.
-ocompatibility=off | legacy | file [,file...]
- Specifies compatibility feature sets. See zpool-features(5) for more information about compatibility feature sets.
- Sets the given pool feature. See the zpool-features(5) section for a list of valid features that can be set. Value can be either disabled or enabled.
- Sets the given file system properties in the root file system of the pool. See the zfsprops(8) manual page for a list of valid properties that can be set.
- Equivalent to
- Sets the in-core pool name to tname while the on-disk name will be the name specified as the pool name pool. This will set the default cachefile property to none. This is intended to handle name space collisions when creating pools for other systems, such as virtual machines or physical machines whose pools live on network block devices.
|August 9, 2019||Debian|