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]
22 .\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
23 .\" Copyright (c) 2013 by Delphix. All rights reserved.
24 .\" Copyright 2017 Nexenta Systems, Inc.
25 .\" Copyright (c) 2017 Datto Inc.
26 .\" Copyright (c) 2017 George Melikov. All Rights Reserved.
33 .Nd configure ZFS storage pools
44 .Ar pool device new_device
53 .Op Fl m Ar mountpoint
54 .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ...
55 .Oo Fl O Ar file-system-property Ns = Ns Ar value Oc Ns ...
72 .Op Fl o Ar field Ns Oo , Ns Ar field Oc Ns ...
73 .Sy all Ns | Ns Ar property Ns Oo , Ns Ar property Oc Ns ...
88 .Op Fl c Ar cachefile Ns | Ns Fl d Ar dir
90 .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ...
96 .Op Fl c Ar cachefile Ns | Ns Fl d Ar dir
98 .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ...
100 .Ar pool Ns | Ns Ar id
105 .Op Fl T Sy u Ns | Ns Sy d
106 .Oo Ar pool Oc Ns ...
107 .Op Ar interval Op Ar count
115 .Op Fl o Ar property Ns Oo , Ns Ar property Oc Ns ...
116 .Op Fl T Sy u Ns | Ns Sy d
117 .Oo Ar pool Oc Ns ...
118 .Op Ar interval Op Ar count
122 .Ar pool Ar device Ns ...
126 .Ar pool Ar device Ns ...
135 .Ar pool Ar device Ns ...
139 .Ar pool Ar device Op Ar new_device
146 .Ar property Ns = Ns Ar value
151 .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ...
157 .Op Fl T Sy u Ns | Ns Sy d
158 .Oo Ar pool Oc Ns ...
159 .Op Ar interval Op Ar count
168 .Fl a Ns | Ns Ar pool Ns ...
172 command configures ZFS storage pools.
173 A storage pool is a collection of devices that provides physical storage and
174 data replication for ZFS datasets.
175 All datasets within a storage pool share the same space.
178 for information on managing datasets.
179 .Ss Virtual Devices (vdevs)
180 A "virtual device" describes a single device or a collection of devices
181 organized according to certain performance and fault characteristics.
182 The following virtual devices are supported:
185 A block device, typically located under
187 ZFS can use individual slices or partitions, though the recommended mode of
188 operation is to use whole disks.
189 A disk can be specified by a full path, or it can be a shorthand name
190 .Po the relative portion of the path under
193 A whole disk can be specified by omitting the slice or partition designation.
197 .Pa /dev/dsk/c0t0d0s2 .
198 When given a whole disk, ZFS automatically labels the disk, if necessary.
201 The use of files as a backing store is strongly discouraged.
202 It is designed primarily for experimental purposes, as the fault tolerance of a
203 file is only as good as the file system of which it is a part.
204 A file must be specified by a full path.
206 A mirror of two or more devices.
207 Data is replicated in an identical fashion across all components of a mirror.
208 A mirror with N disks of size X can hold X bytes and can withstand (N-1) devices
209 failing before data integrity is compromised.
210 .It Sy raidz , raidz1 , raidz2 , raidz3
211 A variation on RAID-5 that allows for better distribution of parity and
212 eliminates the RAID-5
214 .Pq in which data and parity become inconsistent after a power loss .
215 Data and parity is striped across all disks within a raidz group.
217 A raidz group can have single-, double-, or triple-parity, meaning that the
218 raidz group can sustain one, two, or three failures, respectively, without
222 vdev type specifies a single-parity raidz group; the
224 vdev type specifies a double-parity raidz group; and the
226 vdev type specifies a triple-parity raidz group.
229 vdev type is an alias for
232 A raidz group with N disks of size X with P parity disks can hold approximately
233 (N-P)*X bytes and can withstand P device(s) failing before data integrity is
235 The minimum number of devices in a raidz group is one more than the number of
237 The recommended number is between 3 and 9 to help increase performance.
239 A special pseudo-vdev which keeps track of available hot spares for a pool.
240 For more information, see the
244 A separate intent log device.
245 If more than one log device is specified, then writes are load-balanced between
247 Log devices can be mirrored.
248 However, raidz vdev types are not supported for the intent log.
249 For more information, see the
253 A device used to cache storage pool data.
254 A cache device cannot be configured as a mirror or raidz group.
255 For more information, see the
260 Virtual devices cannot be nested, so a mirror or raidz virtual device can only
261 contain files or disks.
263 .Pq or other combinations
266 A pool can have any number of virtual devices at the top of the configuration
270 Data is dynamically distributed across all top-level devices to balance data
272 As new virtual devices are added, ZFS automatically places data on the newly
275 Virtual devices are specified one at a time on the command line, separated by
281 are used to distinguish where a group ends and another begins.
282 For example, the following creates two root vdevs, each a mirror of two disks:
284 # zpool create mypool mirror c0t0d0 c0t1d0 mirror c1t0d0 c1t1d0
286 .Ss Device Failure and Recovery
287 ZFS supports a rich set of mechanisms for handling device failure and data
289 All metadata and data is checksummed, and ZFS automatically repairs bad data
290 from a good copy when corruption is detected.
292 In order to take advantage of these features, a pool must make use of some form
293 of redundancy, using either mirrored or raidz groups.
294 While ZFS supports running in a non-redundant configuration, where each root
295 vdev is simply a disk or file, this is strongly discouraged.
296 A single case of bit corruption can render some or all of your data unavailable.
298 A pool's health status is described by one of three states: online, degraded,
300 An online pool has all devices operating normally.
301 A degraded pool is one in which one or more devices have failed, but the data is
302 still available due to a redundant configuration.
303 A faulted pool has corrupted metadata, or one or more faulted devices, and
304 insufficient replicas to continue functioning.
306 The health of the top-level vdev, such as mirror or raidz device, is
307 potentially impacted by the state of its associated vdevs, or component
309 A top-level vdev or component device is in one of the following states:
310 .Bl -tag -width "DEGRADED"
312 One or more top-level vdevs is in the degraded state because one or more
313 component devices are offline.
314 Sufficient replicas exist to continue functioning.
316 One or more component devices is in the degraded or faulted state, but
317 sufficient replicas exist to continue functioning.
318 The underlying conditions are as follows:
321 The number of checksum errors exceeds acceptable levels and the device is
322 degraded as an indication that something may be wrong.
323 ZFS continues to use the device as necessary.
325 The number of I/O errors exceeds acceptable levels.
326 The device could not be marked as faulted because there are insufficient
327 replicas to continue functioning.
330 One or more top-level vdevs is in the faulted state because one or more
331 component devices are offline.
332 Insufficient replicas exist to continue functioning.
334 One or more component devices is in the faulted state, and insufficient
335 replicas exist to continue functioning.
336 The underlying conditions are as follows:
339 The device could be opened, but the contents did not match expected values.
341 The number of I/O errors exceeds acceptable levels and the device is faulted to
342 prevent further use of the device.
345 The device was explicitly taken offline by the
349 The device is online and functioning.
351 The device was physically removed while the system was running.
352 Device removal detection is hardware-dependent and may not be supported on all
355 The device could not be opened.
356 If a pool is imported when a device was unavailable, then the device will be
357 identified by a unique identifier instead of its path since the path was never
358 correct in the first place.
361 If a device is removed and later re-attached to the system, ZFS attempts
362 to put the device online automatically.
363 Device attach detection is hardware-dependent and might not be supported on all
366 ZFS allows devices to be associated with pools as
368 These devices are not actively used in the pool, but when an active device
369 fails, it is automatically replaced by a hot spare.
370 To create a pool with hot spares, specify a
372 vdev with any number of devices.
375 # zpool create pool mirror c0d0 c1d0 spare c2d0 c3d0
378 Spares can be shared across multiple pools, and can be added with the
380 command and removed with the
383 Once a spare replacement is initiated, a new
385 vdev is created within the configuration that will remain there until the
386 original device is replaced.
387 At this point, the hot spare becomes available again if another device fails.
389 If a pool has a shared spare that is currently being used, the pool can not be
390 exported since other pools may use this shared spare, which may lead to
391 potential data corruption.
393 An in-progress spare replacement can be cancelled by detaching the hot spare.
394 If the original faulted device is detached, then the hot spare assumes its
395 place in the configuration, and is removed from the spare list of all active
398 Spares cannot replace log devices.
400 The ZFS Intent Log (ZIL) satisfies POSIX requirements for synchronous
402 For instance, databases often require their transactions to be on stable storage
403 devices when returning from a system call.
404 NFS and other applications can also use
406 to ensure data stability.
407 By default, the intent log is allocated from blocks within the main pool.
408 However, it might be possible to get better performance using separate intent
409 log devices such as NVRAM or a dedicated disk.
412 # zpool create pool c0d0 c1d0 log c2d0
415 Multiple log devices can also be specified, and they can be mirrored.
418 section for an example of mirroring multiple log devices.
420 Log devices can be added, replaced, attached, detached, and imported and
421 exported as part of the larger pool.
422 Mirrored log devices can be removed by specifying the top-level mirror for the
425 Devices can be added to a storage pool as
427 These devices provide an additional layer of caching between main memory and
429 For read-heavy workloads, where the working set size is much larger than what
430 can be cached in main memory, using cache devices allow much more of this
431 working set to be served from low latency media.
432 Using cache devices provides the greatest performance improvement for random
433 read-workloads of mostly static content.
435 To create a pool with cache devices, specify a
437 vdev with any number of devices.
440 # zpool create pool c0d0 c1d0 cache c2d0 c3d0
443 Cache devices cannot be mirrored or part of a raidz configuration.
444 If a read error is encountered on a cache device, that read I/O is reissued to
445 the original storage pool device, which might be part of a mirrored or raidz
448 The content of the cache devices is considered volatile, as is the case with
451 Each pool has several properties associated with it.
452 Some properties are read-only statistics while others are configurable and
453 change the behavior of the pool.
455 The following are read-only properties:
458 Amount of storage space used within the pool.
460 The size of the system boot partition.
461 This property can only be set at pool creation time and is read-only once pool
463 Setting this property implies using the
467 Percentage of pool space used.
468 This property can also be referred to by its shortened column name,
471 Amount of uninitialized space within the pool or device that can be used to
472 increase the total capacity of the pool.
473 Uninitialized space consists of any space on an EFI labeled vdev which has not
476 .Nm zpool Cm online Fl e
478 This space occurs when a LUN is dynamically expanded.
480 The amount of fragmentation in the pool.
482 The amount of free space available in the pool.
484 After a file system or snapshot is destroyed, the space it was using is
485 returned to the pool asynchronously.
487 is the amount of space remaining to be reclaimed.
494 The current health of the pool.
496 .Sy ONLINE , DEGRADED , FAULTED , OFFLINE, REMOVED , UNAVAIL .
498 A unique identifier for the pool.
500 Total size of the storage pool.
501 .It Sy unsupported@ Ns Em feature_guid
502 Information about unsupported features that are enabled on the pool.
508 The space usage properties report actual physical space available to the
510 The physical space can be different from the total amount of space that any
511 contained datasets can actually use.
512 The amount of space used in a raidz configuration depends on the characteristics
513 of the data being written.
514 In addition, ZFS reserves some space for internal accounting that the
516 command takes into account, but the
519 For non-full pools of a reasonable size, these effects should be invisible.
520 For small pools, or pools that are close to being completely full, these
521 discrepancies may become more noticeable.
523 The following property can be set at creation time and import time:
526 Alternate root directory.
527 If set, this directory is prepended to any mount points within the pool.
528 This can be used when examining an unknown pool where the mount points cannot be
529 trusted, or in an alternate boot environment, where the typical paths are not
532 is not a persistent property.
533 It is valid only while the system is up.
537 .Sy cachefile Ns = Ns Sy none ,
538 though this may be overridden using an explicit setting.
541 The following property can be set only at import time:
543 .It Sy readonly Ns = Ns Sy on Ns | Ns Sy off
546 the pool will be imported in read-only mode.
547 This property can also be referred to by its shortened column name,
551 The following properties can be set at creation time and import time, and later
556 .It Sy autoexpand Ns = Ns Sy on Ns | Ns Sy off
557 Controls automatic pool expansion when the underlying LUN is grown.
560 the pool will be resized according to the size of the expanded device.
561 If the device is part of a mirror or raidz then all devices within that
562 mirror/raidz group must be expanded before the new space is made available to
564 The default behavior is
566 This property can also be referred to by its shortened column name,
568 .It Sy autoreplace Ns = Ns Sy on Ns | Ns Sy off
569 Controls automatic device replacement.
572 device replacement must be initiated by the administrator by using the
577 any new device, found in the same physical location as a device that previously
578 belonged to the pool, is automatically formatted and replaced.
579 The default behavior is
581 This property can also be referred to by its shortened column name,
583 .It Sy bootfs Ns = Ns Ar pool Ns / Ns Ar dataset
584 Identifies the default bootable dataset for the root pool.
585 This property is expected to be set mainly by the installation and upgrade
587 .It Sy cachefile Ns = Ns Ar path Ns | Ns Sy none
588 Controls the location of where the pool configuration is cached.
589 Discovering all pools on system startup requires a cached copy of the
590 configuration data that is stored on the root file system.
591 All pools in this cache are automatically imported when the system boots.
592 Some environments, such as install and clustering, need to cache this
593 information in a different location so that pools are not automatically
595 Setting this property caches the pool configuration in a different location that
596 can later be imported with
597 .Nm zpool Cm import Fl c .
598 Setting it to the special value
600 creates a temporary pool that is never cached, and the special value
603 uses the default location.
605 Multiple pools can share the same cache file.
606 Because the kernel destroys and recreates this file when pools are added and
607 removed, care should be taken when attempting to access this file.
608 When the last pool using a
610 is exported or destroyed, the file is removed.
611 .It Sy comment Ns = Ns Ar text
612 A text string consisting of printable ASCII characters that will be stored
613 such that it is available even if the pool becomes faulted.
614 An administrator can provide additional information about a pool using this
616 .It Sy dedupditto Ns = Ns Ar number
617 Threshold for the number of block ditto copies.
618 If the reference count for a deduplicated block increases above this number, a
619 new ditto copy of this block is automatically stored.
620 The default setting is
622 which causes no ditto copies to be created for deduplicated blocks.
623 The minimum legal nonzero setting is
625 .It Sy delegation Ns = Ns Sy on Ns | Ns Sy off
626 Controls whether a non-privileged user is granted access based on the dataset
627 permissions defined on the dataset.
630 for more information on ZFS delegated administration.
631 .It Sy failmode Ns = Ns Sy wait Ns | Ns Sy continue Ns | Ns Sy panic
632 Controls the system behavior in the event of catastrophic pool failure.
633 This condition is typically a result of a loss of connectivity to the underlying
634 storage device(s) or a failure of all devices within the pool.
635 The behavior of such an event is determined as follows:
636 .Bl -tag -width "continue"
638 Blocks all I/O access until the device connectivity is recovered and the errors
640 This is the default behavior.
644 to any new write I/O requests but allows reads to any of the remaining healthy
646 Any write requests that have yet to be committed to disk would be blocked.
648 Prints out a message to the console and generates a system crash dump.
650 .It Sy feature@ Ns Ar feature_name Ns = Ns Sy enabled
651 The value of this property is the current state of
653 The only valid value when setting this property is
657 to the enabled state.
660 for details on feature states.
661 .It Sy listsnapshots Ns = Ns Sy on Ns | Ns Sy off
662 Controls whether information about snapshots associated with this pool is
670 This property can also be referred to by its shortened name,
672 .It Sy version Ns = Ns Ar version
673 The current on-disk version of the pool.
674 This can be increased, but never decreased.
675 The preferred method of updating pools is with the
677 command, though this property can be used when a specific version is needed for
678 backwards compatibility.
679 Once feature flags are enabled on a pool this property will no longer have a
683 All subcommands that modify state are logged persistently to the pool in their
688 command provides subcommands to create and destroy storage pools, add capacity
689 to storage pools, and provide information about the storage pools.
690 The following subcommands are supported:
696 Displays a help message.
703 Adds the specified virtual devices to the given pool.
706 specification is described in the
711 option, and the device checks performed are described in the
718 even if they appear in use or specify a conflicting replication level.
719 Not all devices can be overridden in this manner.
721 Displays the configuration that would be used without actually adding the
723 The actual pool creation can still fail due to insufficient privileges or
730 .Ar pool device new_device
736 The existing device cannot be part of a raidz configuration.
739 is not currently part of a mirrored configuration,
741 automatically transforms into a two-way mirror of
747 is part of a two-way mirror, attaching
749 creates a three-way mirror, and so on.
752 begins to resilver immediately.
757 even if its appears to be in use.
758 Not all devices can be overridden in this manner.
766 Clears device errors in a pool.
767 If no arguments are specified, all device errors within the pool are cleared.
768 If one or more devices is specified, only those errors associated with the
769 specified device or devices are cleared.
775 .Op Fl m Ar mountpoint
776 .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ...
777 .Oo Fl O Ar file-system-property Ns = Ns Ar value Oc Ns ...
781 Creates a new storage pool containing the virtual devices specified on the
783 The pool name must begin with a letter, and can only contain
784 alphanumeric characters as well as underscore
796 are reserved, as are names beginning with the pattern
800 specification is described in the
804 The command verifies that each device specified is accessible and not currently
805 in use by another subsystem.
806 There are some uses, such as being currently mounted, or specified as the
807 dedicated dump device, that prevents a device from ever being used by ZFS.
808 Other uses, such as having a preexisting UFS file system, can be overridden with
813 The command also checks that the replication strategy for the pool is
815 An attempt to combine redundant and non-redundant storage in a single pool, or
816 to mix disks and files, results in an error unless
819 The use of differently sized devices within a single raidz or mirror group is
820 also flagged as an error unless
826 option is specified, the default mount point is
828 The mount point must not exist or must be empty, or else the root dataset
830 This can be overridden with the
834 By default all supported features are enabled on the new pool unless the
839 Create whole disk pool with EFI System partition to support booting system
841 Default size is 256MB.
842 To create boot partition with custom size, set the
851 Do not enable any features on the new pool.
852 Individual features can be enabled by setting their corresponding properties to
859 for details about feature properties.
863 even if they appear in use or specify a conflicting replication level.
864 Not all devices can be overridden in this manner.
865 .It Fl m Ar mountpoint
866 Sets the mount point for the root dataset.
867 The default mount point is
874 The mount point must be an absolute path,
878 For more information on dataset mount points, see
881 Displays the configuration that would be used without actually creating the
883 The actual pool creation can still fail due to insufficient privileges or
885 .It Fl o Ar property Ns = Ns Ar value
886 Sets the given pool properties.
889 section for a list of valid properties that can be set.
890 .It Fl O Ar file-system-property Ns = Ns Ar value
891 Sets the given file system properties in the root file system of the pool.
896 for a list of valid properties that can be set.
899 .Fl o Sy cachefile Ns = Ns Sy none Fl o Sy altroot Ns = Ns Ar root
907 Destroys the given pool, freeing up any devices for other use.
908 This command tries to unmount any active datasets before destroying the pool.
911 Forces any active datasets contained within the pool to be unmounted.
921 The operation is refused if there are no other valid replicas of the data.
928 Exports the given pools from the system.
929 All devices are marked as exported, but are still considered in use by other
931 The devices can be moved between systems
932 .Pq even those of different endianness
933 and imported as long as a sufficient number of devices are present.
935 Before exporting the pool, all datasets within the pool are unmounted.
936 A pool can not be exported if it has a shared spare that is currently being
939 For pools to be portable, you must give the
941 command whole disks, not just slices, so that ZFS can label the disks with
943 Otherwise, disk drivers on platforms of different endianness will not recognize
947 Forcefully unmount all datasets, using the
951 This command will forcefully export the pool even if it has a shared spare that
952 is currently being used.
953 This may lead to potential data corruption.
959 .Op Fl o Ar field Ns Oo , Ns Ar field Oc Ns ...
960 .Sy all Ns | Ns Ar property Ns Oo , Ns Ar property Oc Ns ...
963 Retrieves the given list of properties
969 for the specified storage pool(s).
970 These properties are displayed with the following fields:
972 name Name of storage pool
973 property Property name
975 source Property source, either 'default' or 'local'.
980 section for more information on the available pool properties.
984 Do not display headers, and separate fields by a single tab instead of arbitrary
987 A comma-separated list of columns to display.
988 .Sy name Ns \&, Ns Sy property Ns \&, Ns Sy value Ns \&, Ns Sy source
989 is the default value.
991 Display numbers in parsable (exact) values.
997 .Oo Ar pool Oc Ns ...
999 Displays the command history of the specified pool(s) or all pools if no pool is
1003 Displays internally logged ZFS events in addition to user initiated events.
1005 Displays log records in long format, which in addition to standard format
1006 includes, the user name, the hostname, and the zone in which the operation was
1015 Lists pools available to import.
1018 option is not specified, this command searches for devices in
1022 option can be specified multiple times, and all directories are searched.
1023 If the device appears to be part of an exported pool, this command displays a
1024 summary of the pool with the name of the pool, a numeric identifier, as well as
1025 the vdev layout and current health of the device for each device or file.
1026 Destroyed pools, pools that were previously destroyed with the
1027 .Nm zpool Cm destroy
1028 command, are not listed unless the
1030 option is specified.
1032 The numeric identifier is unique, and can be used instead of the pool name when
1033 multiple exported pools of the same name are available.
1035 .It Fl c Ar cachefile
1036 Reads configuration from the given
1038 that was created with the
1043 is used instead of searching for devices.
1045 Searches for devices or files in
1049 option can be specified multiple times.
1051 Lists destroyed pools only.
1059 .Op Fl c Ar cachefile Ns | Ns Fl d Ar dir
1061 .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ...
1064 Imports all pools found in the search directories.
1065 Identical to the previous command, except that all pools with a sufficient
1066 number of devices available are imported.
1067 Destroyed pools, pools that were previously destroyed with the
1068 .Nm zpool Cm destroy
1069 command, will not be imported unless the
1071 option is specified.
1074 Searches for and imports all pools found.
1075 .It Fl c Ar cachefile
1076 Reads configuration from the given
1078 that was created with the
1083 is used instead of searching for devices.
1085 Searches for devices or files in
1089 option can be specified multiple times.
1090 This option is incompatible with the
1094 Imports destroyed pools only.
1097 option is also required.
1099 Forces import, even if the pool appears to be potentially active.
1101 Recovery mode for a non-importable pool.
1102 Attempt to return the pool to an importable state by discarding the last few
1104 Not all damaged pools can be recovered by using this option.
1105 If successful, the data from the discarded transactions is irretrievably lost.
1106 This option is ignored if the pool is importable or already imported.
1108 Allows a pool to import when there is a missing log device.
1109 Recent transactions can be lost because the log device will be discarded.
1114 Determines whether a non-importable pool can be made importable again, but does
1115 not actually perform the pool recovery.
1116 For more details about pool recovery mode, see the
1120 Import the pool without mounting any file systems.
1122 Comma-separated list of mount options to use when mounting datasets within the
1126 for a description of dataset properties and mount options.
1127 .It Fl o Ar property Ns = Ns Ar value
1128 Sets the specified property on the imported pool.
1131 section for more information on the available pool properties.
1147 .Op Fl c Ar cachefile Ns | Ns Fl d Ar dir
1149 .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ...
1151 .Ar pool Ns | Ns Ar id
1154 Imports a specific pool.
1155 A pool can be identified by its name or the numeric identifier.
1158 is specified, the pool is imported using the name
1160 Otherwise, it is imported with the same name as its exported name.
1162 If a device is removed from a system without running
1164 first, the device appears as potentially active.
1165 It cannot be determined if this was a failed export, or whether the device is
1166 really in use from another host.
1167 To import a pool in this state, the
1171 .It Fl c Ar cachefile
1172 Reads configuration from the given
1174 that was created with the
1179 is used instead of searching for devices.
1181 Searches for devices or files in
1185 option can be specified multiple times.
1186 This option is incompatible with the
1190 Imports destroyed pool.
1193 option is also required.
1195 Forces import, even if the pool appears to be potentially active.
1197 Recovery mode for a non-importable pool.
1198 Attempt to return the pool to an importable state by discarding the last few
1200 Not all damaged pools can be recovered by using this option.
1201 If successful, the data from the discarded transactions is irretrievably lost.
1202 This option is ignored if the pool is importable or already imported.
1204 Allows a pool to import when there is a missing log device.
1205 Recent transactions can be lost because the log device will be discarded.
1210 Determines whether a non-importable pool can be made importable again, but does
1211 not actually perform the pool recovery.
1212 For more details about pool recovery mode, see the
1216 Comma-separated list of mount options to use when mounting datasets within the
1220 for a description of dataset properties and mount options.
1221 .It Fl o Ar property Ns = Ns Ar value
1222 Sets the specified property on the imported pool.
1225 section for more information on the available pool properties.
1240 .Op Fl T Sy u Ns | Ns Sy d
1241 .Oo Ar pool Oc Ns ...
1242 .Op Ar interval Op Ar count
1244 Displays I/O statistics for the given pools.
1247 the statistics are printed every
1249 seconds until ^C is pressed.
1252 are specified, statistics for every pool in the system is shown.
1255 is specified, the command exits after
1257 reports are printed.
1259 .It Fl T Sy u Ns | Ns Sy d
1260 Display a time stamp.
1263 for a printed representation of the internal representation of time.
1268 for standard date format.
1272 Verbose statistics Reports usage statistics for individual vdevs within the
1273 pool, in addition to the pool-wide statistics.
1281 Removes ZFS label information from the specified
1285 must not be part of an active pool configuration.
1288 Treat exported or foreign devices as inactive.
1294 .Op Fl o Ar property Ns Oo , Ns Ar property Oc Ns ...
1295 .Op Fl T Sy u Ns | Ns Sy d
1296 .Oo Ar pool Oc Ns ...
1297 .Op Ar interval Op Ar count
1299 Lists the given pools along with a health status and space usage.
1302 are specified, all pools in the system are listed.
1305 the information is printed every
1307 seconds until ^C is pressed.
1310 is specified, the command exits after
1312 reports are printed.
1316 Do not display headers, and separate fields by a single tab instead of arbitrary
1318 .It Fl o Ar property
1319 Comma-separated list of properties to display.
1322 section for a list of valid properties.
1324 .Cm name , size , allocated , free , expandsize , fragmentation , capacity ,
1325 .Cm dedupratio , health , altroot .
1327 Display numbers in parsable
1330 .It Fl T Sy u Ns | Ns Sy d
1331 Display a time stamp.
1334 for a printed representation of the internal representation of time.
1339 for standard date format.
1344 Reports usage statistics for individual vdevs within the pool, in addition to
1345 the pool-wise statistics.
1351 .Ar pool Ar device Ns ...
1353 Takes the specified physical device offline.
1356 is offline, no attempt is made to read or write to the device.
1357 This command is not applicable to spares.
1361 Upon reboot, the specified physical device reverts to its previous state.
1367 .Ar pool Ar device Ns ...
1369 Brings the specified physical device online.
1370 This command is not applicable to spares.
1373 Expand the device to use all available space.
1374 If the device is part of a mirror or raidz then all devices must be expanded
1375 before the new space will become available to the pool.
1382 Generates a new unique identifier for the pool.
1383 You must ensure that all devices in this pool are online and healthy before
1384 performing this action.
1390 Reopen all the vdevs associated with the pool.
1394 .Ar pool Ar device Ns ...
1396 Removes the specified device from the pool.
1397 This command currently only supports removing hot spares, cache, and log
1399 A mirrored log device can be removed by specifying the top-level mirror for the
1401 Non-log devices that are part of a mirrored configuration can be removed using
1405 Non-redundant and raidz devices cannot be removed from a pool.
1410 .Ar pool Ar device Op Ar new_device
1416 This is equivalent to attaching
1418 waiting for it to resilver, and then detaching
1423 must be greater than or equal to the minimum size of all the devices in a mirror
1424 or raidz configuration.
1427 is required if the pool is not redundant.
1430 is not specified, it defaults to
1432 This form of replacement is useful after an existing disk has failed and has
1433 been physically replaced.
1434 In this case, the new disk may have the same
1436 path as the old device, even though it is actually a different disk.
1437 ZFS recognizes this.
1442 even if its appears to be in use.
1443 Not all devices can be overridden in this manner.
1451 Begins a scrub or resumes a paused scrub.
1452 The scrub examines all data in the specified pools to verify that it checksums
1456 devices, ZFS automatically repairs any damage discovered during the scrub.
1459 command reports the progress of the scrub and summarizes the results of the
1460 scrub upon completion.
1462 Scrubbing and resilvering are very similar operations.
1463 The difference is that resilvering only examines data that ZFS knows to be out
1466 for example, when attaching a new device to a mirror or replacing an existing
1469 whereas scrubbing examines all data to discover silent errors due to hardware
1470 faults or disk failure.
1472 Because scrubbing and resilvering are I/O-intensive operations, ZFS only allows
1474 If a scrub is paused, the
1477 If a resilver is in progress, ZFS does not allow a scrub to be started until the
1486 Scrub pause state and progress are periodically synced to disk.
1487 If the system is restarted or pool is exported during a paused scrub,
1488 even after import, scrub will remain paused until it is resumed.
1489 Once resumed the scrub will pick up from the place where it was last
1490 checkpointed to disk.
1491 To resume a paused scrub issue
1498 .Ar property Ns = Ns Ar value
1501 Sets the given property on the specified pool.
1504 section for more information on what properties can be set and acceptable
1510 .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ...
1521 At the time of the split,
1523 will be a replica of
1527 Do dry run, do not actually perform the split.
1528 Print out the expected configuration of
1530 .It Fl o Ar property Ns = Ns Ar value
1531 Sets the specified property for
1535 section for more information on the available pool properties.
1543 and automatically import it.
1549 .Op Fl T Sy u Ns | Ns Sy d
1550 .Oo Ar pool Oc Ns ...
1551 .Op Ar interval Op Ar count
1553 Displays the detailed health status for the given pools.
1556 is specified, then the status of each pool in the system is displayed.
1557 For more information on pool and device health, see the
1558 .Sx Device Failure and Recovery
1561 If a scrub or resilver is in progress, this command reports the percentage done
1562 and the estimated time to completion.
1563 Both of these are only approximate, because the amount of data in the pool and
1564 the other workloads on the system can change.
1567 Display a histogram of deduplication statistics, showing the allocated
1568 .Pq physically present on disk
1570 .Pq logically referenced in the pool
1571 block counts and sizes by reference count.
1572 .It Fl T Sy u Ns | Ns Sy d
1573 Display a time stamp.
1576 for a printed representation of the internal representation of time.
1581 for standard date format.
1585 Displays verbose data error information, printing out a complete list of all
1586 data errors since the last complete pool scrub.
1588 Only display status for pools that are exhibiting errors or are otherwise
1590 Warnings about pools not using the latest on-disk format will not be included.
1596 Displays pools which do not have all supported features enabled and pools
1597 formatted using a legacy ZFS version number.
1598 These pools can continue to be used, but some features may not be available.
1600 .Nm zpool Cm upgrade Fl a
1601 to enable all features on all pools.
1607 Displays legacy ZFS versions supported by the current software.
1609 .Xr zpool-features 5
1610 for a description of feature flags features supported by the current software.
1615 .Fl a Ns | Ns Ar pool Ns ...
1617 Enables all supported features on the given pool.
1618 Once this is done, the pool will no longer be accessible on systems that do not
1619 support feature flags.
1621 .Xr zpool-features 5
1622 for details on compatibility with systems that support feature flags, but do not
1623 support all features enabled on the pool.
1626 Enables all supported features on all pools.
1628 Upgrade to the specified legacy version.
1631 flag is specified, no features will be enabled on the pool.
1632 This option can only be used to increase the version number up to the last
1633 supported legacy version number.
1637 The following exit values are returned:
1640 Successful completion.
1644 Invalid command line options were specified.
1648 .It Sy Example 1 No Creating a RAID-Z Storage Pool
1649 The following command creates a pool with a single raidz root vdev that
1650 consists of six disks.
1652 # zpool create tank raidz c0t0d0 c0t1d0 c0t2d0 c0t3d0 c0t4d0 c0t5d0
1654 .It Sy Example 2 No Creating a Mirrored Storage Pool
1655 The following command creates a pool with two mirrors, where each mirror
1658 # zpool create tank mirror c0t0d0 c0t1d0 mirror c0t2d0 c0t3d0
1660 .It Sy Example 3 No Creating a ZFS Storage Pool by Using Slices
1661 The following command creates an unmirrored pool using two disk slices.
1663 # zpool create tank /dev/dsk/c0t0d0s1 c0t1d0s4
1665 .It Sy Example 4 No Creating a ZFS Storage Pool by Using Files
1666 The following command creates an unmirrored pool using files.
1667 While not recommended, a pool based on files can be useful for experimental
1670 # zpool create tank /path/to/file/a /path/to/file/b
1672 .It Sy Example 5 No Adding a Mirror to a ZFS Storage Pool
1673 The following command adds two mirrored disks to the pool
1675 assuming the pool is already made up of two-way mirrors.
1676 The additional space is immediately available to any datasets within the pool.
1678 # zpool add tank mirror c1t0d0 c1t1d0
1680 .It Sy Example 6 No Listing Available ZFS Storage Pools
1681 The following command lists all available pools on the system.
1682 In this case, the pool
1684 is faulted due to a missing device.
1685 The results from this command are similar to the following:
1688 NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT
1689 rpool 19.9G 8.43G 11.4G 33% - 42% 1.00x ONLINE -
1690 tank 61.5G 20.0G 41.5G 48% - 32% 1.00x ONLINE -
1691 zion - - - - - - - FAULTED -
1693 .It Sy Example 7 No Destroying a ZFS Storage Pool
1694 The following command destroys the pool
1696 and any datasets contained within.
1698 # zpool destroy -f tank
1700 .It Sy Example 8 No Exporting a ZFS Storage Pool
1701 The following command exports the devices in pool
1703 so that they can be relocated or later imported.
1707 .It Sy Example 9 No Importing a ZFS Storage Pool
1708 The following command displays available pools, and then imports the pool
1710 for use on the system.
1711 The results from this command are similar to the following:
1715 id: 15451357997522795478
1717 action: The pool can be imported using its name or numeric identifier.
1727 .It Sy Example 10 No Upgrading All ZFS Storage Pools to the Current Version
1728 The following command upgrades all ZFS Storage pools to the current version of
1732 This system is currently running ZFS version 2.
1734 .It Sy Example 11 No Managing Hot Spares
1735 The following command creates a new pool with an available hot spare:
1737 # zpool create tank mirror c0t0d0 c0t1d0 spare c0t2d0
1740 If one of the disks were to fail, the pool would be reduced to the degraded
1742 The failed device can be replaced using the following command:
1744 # zpool replace tank c0t0d0 c0t3d0
1747 Once the data has been resilvered, the spare is automatically removed and is
1748 made available for use should another device fail.
1749 The hot spare can be permanently removed from the pool using the following
1752 # zpool remove tank c0t2d0
1754 .It Sy Example 12 No Creating a ZFS Pool with Mirrored Separate Intent Logs
1755 The following command creates a ZFS storage pool consisting of two, two-way
1756 mirrors and mirrored log devices:
1758 # zpool create pool mirror c0d0 c1d0 mirror c2d0 c3d0 log mirror \e
1761 .It Sy Example 13 No Adding Cache Devices to a ZFS Pool
1762 The following command adds two disks for use as cache devices to a ZFS storage
1765 # zpool add pool cache c2d0 c3d0
1768 Once added, the cache devices gradually fill with content from main memory.
1769 Depending on the size of your cache devices, it could take over an hour for
1771 Capacity and reads can be monitored using the
1775 # zpool iostat -v pool 5
1777 .It Sy Example 14 No Removing a Mirrored Log Device
1778 The following command removes the mirrored log device
1780 Given this configuration:
1784 scrub: none requested
1787 NAME STATE READ WRITE CKSUM
1789 mirror-0 ONLINE 0 0 0
1792 mirror-1 ONLINE 0 0 0
1796 mirror-2 ONLINE 0 0 0
1801 The command to remove the mirrored log
1805 # zpool remove tank mirror-2
1807 .It Sy Example 15 No Displaying expanded space on a device
1808 The following command displays the detailed information for the pool
1810 This pool is comprised of a single raidz vdev where one of its devices
1811 increased its capacity by 10GB.
1812 In this example, the pool will not be able to utilize this extra capacity until
1813 all the devices under the raidz vdev have been expanded.
1815 # zpool list -v data
1816 NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT
1817 data 23.9G 14.6G 9.30G 48% - 61% 1.00x ONLINE -
1818 raidz1 23.9G 14.6G 9.30G 48% -
1824 .Sh INTERFACE STABILITY
1829 .Xr zpool-features 5