]> git.proxmox.com Git - mirror_zfs.git/blame - man/man8/zpool.8
Improve zfs-module-parameters(5)
[mirror_zfs.git] / man / man8 / zpool.8
CommitLineData
058ac9ba
BB
1'\" te
2.\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
d96eb2b1 3.\" Copyright 2011 Nexenta Systems, Inc. All rights reserved.
f3a7f661 4.\" Copyright (c) 2013 by Delphix. All rights reserved.
df831108 5.\" Copyright (c) 2012 Cyril Plisko. All Rights Reserved.
9ae529ec
CS
6.\" The contents of this file are subject to the terms of the Common Development
7.\" and Distribution License (the "License"). You may not use this file except
8.\" in compliance with the License. You can obtain a copy of the license at
9.\" usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
10.\"
11.\" See the License for the specific language governing permissions and
12.\" limitations under the License. When distributing Covered Code, include this
13.\" CDDL HEADER in each file and include the License file at
14.\" usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this
15.\" CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your
16.\" own identifying information:
17.\" Portions Copyright [yyyy] [name of copyright owner]
6a107f41 18.TH zpool 8 "May 11, 2016" "ZFS pool 28, filesystem 5" "System Administration Commands"
058ac9ba
BB
19.SH NAME
20zpool \- configures ZFS storage pools
21.SH SYNOPSIS
22.LP
23.nf
24\fBzpool\fR [\fB-?\fR]
25.fi
26
27.LP
28.nf
a77f29f9 29\fBzpool add\fR [\fB-fgLnP\fR] [\fB-o\fR \fIproperty=value\fR] \fIpool\fR \fIvdev\fR ...
058ac9ba
BB
30.fi
31
32.LP
33.nf
df831108 34\fBzpool attach\fR [\fB-f\fR] [\fB-o\fR \fIproperty=value\fR] \fIpool\fR \fIdevice\fR \fInew_device\fR
058ac9ba
BB
35.fi
36
37.LP
38.nf
39\fBzpool clear\fR \fIpool\fR [\fIdevice\fR]
40.fi
41
42.LP
43.nf
9ae529ec 44\fBzpool create\fR [\fB-fnd\fR] [\fB-o\fR \fIproperty=value\fR] ... [\fB-O\fR \fIfile-system-property=value\fR]
83e9986f 45 ... [\fB-m\fR \fImountpoint\fR] [\fB-R\fR \fIroot\fR] [\fB-t\fR \fItname\fR] \fIpool\fR \fIvdev\fR ...
058ac9ba
BB
46.fi
47
48.LP
49.nf
50\fBzpool destroy\fR [\fB-f\fR] \fIpool\fR
51.fi
52
53.LP
54.nf
55\fBzpool detach\fR \fIpool\fR \fIdevice\fR
56.fi
57
d050c627
TF
58.LP
59.nf
60\fBzpool events\fR [\fB-vHfc\fR] [\fIpool\fR] ...
61.fi
62
058ac9ba
BB
63.LP
64.nf
859735c0 65\fBzpool export\fR [\fB-a\fR] [\fB-f\fR] \fIpool\fR ...
058ac9ba
BB
66.fi
67
68.LP
69.nf
2a8b84b7 70\fBzpool get\fR [\fB-Hp\fR] [\fB-o \fR\fIfield\fR[,...]] "\fIall\fR" | \fIproperty\fR[,...] \fIpool\fR ...
058ac9ba
BB
71.fi
72
73.LP
74.nf
75\fBzpool history\fR [\fB-il\fR] [\fIpool\fR] ...
76.fi
77
78.LP
79.nf
80\fBzpool import\fR [\fB-d\fR \fIdir\fR] [\fB-D\fR]
81.fi
82
83.LP
84.nf
7f9d9946 85\fBzpool import\fR [\fB-o \fImntopts\fR\fR] [\fB-o\fR \fIproperty=value\fR] ... [\fB-d\fR \fIdir\fR | \fB-c\fR \fIcachefile\fR]
7d11e37e 86 [\fB-D\fR] [\fB-f\fR] [\fB-m\fR] [\fB-N\fR] [\fB-R\fR \fIroot\fR] [\fB-F\fR [\fB-n\fR] [\fB-X\fR\] [\fB-T\fR\]] [\fB-s\fR] \fB-a\fR
058ac9ba
BB
87.fi
88
89.LP
90.nf
91\fBzpool import\fR [\fB-o \fImntopts\fR\fR] [\fB-o\fR \fIproperty=value\fR] ... [\fB-d\fR \fIdir\fR | \fB-c\fR \fIcachefile\fR]
7d11e37e
BB
92 [\fB-D\fR] [\fB-f\fR] [\fB-m\fR] [\fB-R\fR \fIroot\fR] [\fB-F\fR [\fB-n\fR] [\fB-X\fR] [\fB-T\fR\]] [\fB-t\fR]] [\fB-s\fR]
93 \fIpool\fR | \fIid\fR [\fInewpool\fR]
058ac9ba
BB
94.fi
95
96.LP
97.nf
193a37cb
TH
98\fB\fBzpool iostat\fR [\fB-T\fR \fBd\fR | \fBu\fR] [\fB-ghHLpPvy\fR] [\fB-G\fR|[\fB-lq\fR]]
99 [[\fIpool\fR ...]|[\fIpool vdev\fR ...]|[\fIvdev\fR ...]] [\fIinterval\fR[\fIcount\fR]]\fR
100
058ac9ba
BB
101.fi
102
131cc95c
DK
103.LP
104.nf
105\fBzpool labelclear\fR [\fB-f\fR] \fIdevice\fR
106.fi
107
058ac9ba
BB
108.LP
109.nf
2a8b84b7 110\fBzpool list\fR [\fB-T\fR d | u ] [\fB-HgLpPv\fR] [\fB-o\fR \fIproperty\fR[,...]] [\fIpool\fR] ...
2e2ddc30 111 [\fIinterval\fR[\fIcount\fR]]
058ac9ba
BB
112.fi
113
114.LP
115.nf
116\fBzpool offline\fR [\fB-t\fR] \fIpool\fR \fIdevice\fR ...
117.fi
118
119.LP
120.nf
121\fBzpool online\fR \fIpool\fR \fIdevice\fR ...
122.fi
123
3541dc6d
GA
124.LP
125.nf
126\fBzpool reguid\fR \fIpool\fR
127.fi
128
5853fe79
GW
129.LP
130.nf
131\fBzpool reopen\fR \fIpool\fR
132.fi
133
058ac9ba
BB
134.LP
135.nf
136\fBzpool remove\fR \fIpool\fR \fIdevice\fR ...
137.fi
138
139.LP
140.nf
628668a3 141\fBzpool replace\fR [\fB-f\fR] [\fB-o\fR \fIproperty=value\fR] \fIpool\fR \fIdevice\fR [\fInew_device\fR]
058ac9ba
BB
142.fi
143
144.LP
145.nf
146\fBzpool scrub\fR [\fB-s\fR] \fIpool\fR ...
147.fi
148
149.LP
150.nf
151\fBzpool set\fR \fIproperty\fR=\fIvalue\fR \fIpool\fR
152.fi
153
fb827006
SB
154.LP
155.nf
a77f29f9 156\fBzpool split\fR [\fB-gLnP\fR] [\fB-R\fR \fIaltroot\fR] [\fB-o\fR \fIproperty=value\fR] \fIpool\fR \fInewpool\fR [\fIdevice\fR ...]
fb827006
SB
157.fi
158
058ac9ba
BB
159.LP
160.nf
a77f29f9 161\fBzpool status\fR [\fB-gLPvxD\fR] [\fB-T\fR d | u] [\fIpool\fR] ... [\fIinterval\fR [\fIcount\fR]]
058ac9ba
BB
162.fi
163
164.LP
165.nf
6b4e21c6 166\fBzpool upgrade\fR
058ac9ba
BB
167.fi
168
169.LP
170.nf
171\fBzpool upgrade\fR \fB-v\fR
172.fi
173
174.LP
175.nf
176\fBzpool upgrade\fR [\fB-V\fR \fIversion\fR] \fB-a\fR | \fIpool\fR ...
177.fi
178
179.SH DESCRIPTION
180.sp
181.LP
182The \fBzpool\fR command configures \fBZFS\fR storage pools. A storage pool is a collection of devices that provides physical storage and data replication for \fBZFS\fR datasets.
183.sp
184.LP
2d1b7b0b 185All datasets within a storage pool share the same space. See \fBzfs\fR(8) for information on managing datasets.
058ac9ba
BB
186.SS "Virtual Devices (\fBvdev\fRs)"
187.sp
188.LP
189A "virtual device" describes a single device or a collection of devices organized according to certain performance and fault characteristics. The following virtual devices are supported:
190.sp
191.ne 2
058ac9ba
BB
192.na
193\fB\fBdisk\fR\fR
194.ad
195.RS 10n
25d4782b 196A block device, typically located under \fB/dev\fR. \fBZFS\fR can use individual partitions, though the recommended mode of operation is to use whole disks. A disk can be specified by a full path, or it can be a shorthand name (the relative portion of the path under "/dev"). For example, "sda" is equivalent to "/dev/sda". A whole disk can be specified by omitting the partition designation. When given a whole disk, \fBZFS\fR automatically labels the disk, if necessary.
058ac9ba
BB
197.RE
198
199.sp
200.ne 2
058ac9ba
BB
201.na
202\fB\fBfile\fR\fR
203.ad
204.RS 10n
058ac9ba
BB
205A regular file. The use of files as a backing store is strongly discouraged. It is designed primarily for experimental purposes, as the fault tolerance of a file is only as good as the file system of which it is a part. A file must be specified by a full path.
206.RE
207
208.sp
209.ne 2
058ac9ba
BB
210.na
211\fB\fBmirror\fR\fR
212.ad
213.RS 10n
058ac9ba
BB
214A mirror of two or more devices. Data is replicated in an identical fashion across all components of a mirror. A mirror with \fIN\fR disks of size \fIX\fR can hold \fIX\fR bytes and can withstand (\fIN-1\fR) devices failing before data integrity is compromised.
215.RE
216
217.sp
218.ne 2
058ac9ba
BB
219.na
220\fB\fBraidz\fR\fR
221.ad
222.br
223.na
224\fB\fBraidz1\fR\fR
225.ad
226.br
227.na
228\fB\fBraidz2\fR\fR
229.ad
230.br
231.na
232\fB\fBraidz3\fR\fR
233.ad
234.RS 10n
058ac9ba
BB
235A variation on \fBRAID-5\fR that allows for better distribution of parity and eliminates the "\fBRAID-5\fR write hole" (in which data and parity become inconsistent after a power loss). Data and parity is striped across all disks within a \fBraidz\fR group.
236.sp
237A \fBraidz\fR group can have single-, double- , or triple parity, meaning that the \fBraidz\fR group can sustain one, two, or three failures, respectively, without losing any data. The \fBraidz1\fR \fBvdev\fR type specifies a single-parity \fBraidz\fR group; the \fBraidz2\fR \fBvdev\fR type specifies a double-parity \fBraidz\fR group; and the \fBraidz3\fR \fBvdev\fR type specifies a triple-parity \fBraidz\fR group. The \fBraidz\fR \fBvdev\fR type is an alias for \fBraidz1\fR.
238.sp
239A \fBraidz\fR group with \fIN\fR disks of size \fIX\fR with \fIP\fR parity disks can hold approximately (\fIN-P\fR)*\fIX\fR bytes and can withstand \fIP\fR device(s) failing before data integrity is compromised. The minimum number of devices in a \fBraidz\fR group is one more than the number of parity disks. The recommended number is between 3 and 9 to help increase performance.
240.RE
241
242.sp
243.ne 2
058ac9ba
BB
244.na
245\fB\fBspare\fR\fR
246.ad
247.RS 10n
058ac9ba
BB
248A special pseudo-\fBvdev\fR which keeps track of available hot spares for a pool. For more information, see the "Hot Spares" section.
249.RE
250
251.sp
252.ne 2
058ac9ba
BB
253.na
254\fB\fBlog\fR\fR
255.ad
256.RS 10n
058ac9ba
BB
257A separate-intent log device. If more than one log device is specified, then writes are load-balanced between devices. Log devices can be mirrored. However, \fBraidz\fR \fBvdev\fR types are not supported for the intent log. For more information, see the "Intent Log" section.
258.RE
259
260.sp
261.ne 2
058ac9ba
BB
262.na
263\fB\fBcache\fR\fR
264.ad
265.RS 10n
15313c5e 266A device used to cache storage pool data. A cache device cannot be configured as a mirror or \fBraidz\fR group. For more information, see the "Cache Devices" section.
058ac9ba
BB
267.RE
268
269.sp
270.LP
271Virtual devices cannot be nested, so a mirror or \fBraidz\fR virtual device can only contain files or disks. Mirrors of mirrors (or other combinations) are not allowed.
272.sp
273.LP
274A pool can have any number of virtual devices at the top of the configuration (known as "root vdevs"). Data is dynamically distributed across all top-level devices to balance data among devices. As new virtual devices are added, \fBZFS\fR automatically places data on the newly available devices.
275.sp
276.LP
277Virtual devices are specified one at a time on the command line, separated by whitespace. The keywords "mirror" and "raidz" are used to distinguish where a group ends and another begins. For example, the following creates two root vdevs, each a mirror of two disks:
278.sp
279.in +2
280.nf
54e5f226 281# \fBzpool create mypool mirror sda sdb mirror sdc sdd\fR
058ac9ba
BB
282.fi
283.in -2
284.sp
285
286.SS "Device Failure and Recovery"
287.sp
288.LP
289\fBZFS\fR supports a rich set of mechanisms for handling device failure and data corruption. All metadata and data is checksummed, and \fBZFS\fR automatically repairs bad data from a good copy when corruption is detected.
290.sp
291.LP
292In order to take advantage of these features, a pool must make use of some form of redundancy, using either mirrored or \fBraidz\fR groups. While \fBZFS\fR supports running in a non-redundant configuration, where each root vdev is simply a disk or file, this is strongly discouraged. A single case of bit corruption can render some or all of your data unavailable.
293.sp
294.LP
6b4e21c6 295A pool's health status is described by one of three states: online, degraded, or faulted. An online pool has all devices operating normally. A degraded pool is one in which one or more devices have failed, but the data is still available due to a redundant configuration. A faulted pool has corrupted metadata, or one or more faulted devices, and insufficient replicas to continue functioning.
058ac9ba
BB
296.sp
297.LP
298The health of the top-level vdev, such as mirror or \fBraidz\fR device, is potentially impacted by the state of its associated vdevs, or component devices. A top-level vdev or component device is in one of the following states:
299.sp
300.ne 2
058ac9ba
BB
301.na
302\fB\fBDEGRADED\fR\fR
303.ad
304.RS 12n
058ac9ba
BB
305One or more top-level vdevs is in the degraded state because one or more component devices are offline. Sufficient replicas exist to continue functioning.
306.sp
307One or more component devices is in the degraded or faulted state, but sufficient replicas exist to continue functioning. The underlying conditions are as follows:
308.RS +4
309.TP
310.ie t \(bu
311.el o
312The number of checksum errors exceeds acceptable levels and the device is degraded as an indication that something may be wrong. \fBZFS\fR continues to use the device as necessary.
313.RE
314.RS +4
315.TP
316.ie t \(bu
317.el o
318The number of I/O errors exceeds acceptable levels. The device could not be marked as faulted because there are insufficient replicas to continue functioning.
319.RE
320.RE
321
322.sp
323.ne 2
058ac9ba
BB
324.na
325\fB\fBFAULTED\fR\fR
326.ad
327.RS 12n
6b4e21c6 328One or more top-level vdevs is in the faulted state because one or more component devices are offline. Insufficient replicas exist to continue functioning.
058ac9ba
BB
329.sp
330One or more component devices is in the faulted state, and insufficient replicas exist to continue functioning. The underlying conditions are as follows:
331.RS +4
332.TP
333.ie t \(bu
334.el o
6b4e21c6 335The device could be opened, but the contents did not match expected values.
058ac9ba
BB
336.RE
337.RS +4
338.TP
339.ie t \(bu
340.el o
341The number of I/O errors exceeds acceptable levels and the device is faulted to prevent further use of the device.
342.RE
343.RE
344
345.sp
346.ne 2
058ac9ba
BB
347.na
348\fB\fBOFFLINE\fR\fR
349.ad
350.RS 12n
058ac9ba
BB
351The device was explicitly taken offline by the "\fBzpool offline\fR" command.
352.RE
353
354.sp
355.ne 2
058ac9ba
BB
356.na
357\fB\fBONLINE\fR\fR
358.ad
359.RS 12n
058ac9ba
BB
360The device is online and functioning.
361.RE
362
363.sp
364.ne 2
058ac9ba
BB
365.na
366\fB\fBREMOVED\fR\fR
367.ad
368.RS 12n
058ac9ba
BB
369The device was physically removed while the system was running. Device removal detection is hardware-dependent and may not be supported on all platforms.
370.RE
371
372.sp
373.ne 2
058ac9ba
BB
374.na
375\fB\fBUNAVAIL\fR\fR
376.ad
377.RS 12n
058ac9ba
BB
378The device could not be opened. If a pool is imported when a device was unavailable, then the device will be identified by a unique identifier instead of its path since the path was never correct in the first place.
379.RE
380
381.sp
382.LP
383If a device is removed and later re-attached to the system, \fBZFS\fR attempts to put the device online automatically. Device attach detection is hardware-dependent and might not be supported on all platforms.
384.SS "Hot Spares"
385.sp
386.LP
6b4e21c6 387\fBZFS\fR allows devices to be associated with pools as "hot spares". These devices are not actively used in the pool, but when an active device fails, it is automatically replaced by a hot spare. To create a pool with hot spares, specify a "spare" \fBvdev\fR with any number of devices. For example,
058ac9ba
BB
388.sp
389.in +2
390.nf
54e5f226 391# zpool create pool mirror sda sdb spare sdc sdd
058ac9ba
BB
392.fi
393.in -2
394.sp
395
396.sp
397.LP
0d122e21 398Spares can be shared across multiple pools, and can be added with the "\fBzpool add\fR" command and removed with the "\fBzpool remove\fR" command. Once a spare replacement is initiated, a new "spare" \fBvdev\fR is created within the configuration that will remain there until the original device is replaced. At this point, the hot spare becomes available again.
058ac9ba
BB
399.sp
400.LP
401If a pool has a shared spare that is currently being used, the pool can not be exported since other pools may use this shared spare, which may lead to potential data corruption.
402.sp
403.LP
404An in-progress spare replacement can be cancelled by detaching the hot spare. If the original faulted device is detached, then the hot spare assumes its place in the configuration, and is removed from the spare list of all active pools.
405.sp
406.LP
407Spares cannot replace log devices.
408.SS "Intent Log"
409.sp
410.LP
411The \fBZFS\fR Intent Log (\fBZIL\fR) satisfies \fBPOSIX\fR requirements for synchronous transactions. For instance, databases often require their transactions to be on stable storage devices when returning from a system call. \fBNFS\fR and other applications can also use \fBfsync\fR() to ensure data stability. By default, the intent log is allocated from blocks within the main pool. However, it might be possible to get better performance using separate intent log devices such as \fBNVRAM\fR or a dedicated disk. For example:
412.sp
413.in +2
414.nf
54e5f226 415\fB# zpool create pool sda sdb log sdc\fR
058ac9ba
BB
416.fi
417.in -2
418.sp
419
420.sp
421.LP
422Multiple log devices can also be specified, and they can be mirrored. See the EXAMPLES section for an example of mirroring multiple log devices.
423.sp
424.LP
425Log devices can be added, replaced, attached, detached, and imported and exported as part of the larger pool. Mirrored log devices can be removed by specifying the top-level mirror for the log.
426.SS "Cache Devices"
427.sp
428.LP
429Devices can be added to a storage pool as "cache devices." These devices provide an additional layer of caching between main memory and disk. For read-heavy workloads, where the working set size is much larger than what can be cached in main memory, using cache devices allow much more of this working set to be served from low latency media. Using cache devices provides the greatest performance improvement for random read-workloads of mostly static content.
430.sp
431.LP
432To create a pool with cache devices, specify a "cache" \fBvdev\fR with any number of devices. For example:
433.sp
434.in +2
435.nf
54e5f226 436\fB# zpool create pool sda sdb cache sdc sdd\fR
058ac9ba
BB
437.fi
438.in -2
439.sp
440
441.sp
442.LP
443Cache devices cannot be mirrored or part of a \fBraidz\fR configuration. If a read error is encountered on a cache device, that read \fBI/O\fR is reissued to the original storage pool device, which might be part of a mirrored or \fBraidz\fR configuration.
444.sp
445.LP
446The content of the cache devices is considered volatile, as is the case with other system caches.
447.SS "Properties"
448.sp
449.LP
450Each pool has several properties associated with it. Some properties are read-only statistics while others are configurable and change the behavior of the pool. The following are read-only properties:
451.sp
452.ne 2
058ac9ba
BB
453.na
454\fB\fBavailable\fR\fR
455.ad
456.RS 20n
058ac9ba
BB
457Amount of storage available within the pool. This property can also be referred to by its shortened column name, "avail".
458.RE
459
460.sp
461.ne 2
058ac9ba
BB
462.na
463\fB\fBcapacity\fR\fR
464.ad
465.RS 20n
058ac9ba
BB
466Percentage of pool space used. This property can also be referred to by its shortened column name, "cap".
467.RE
468
d96eb2b1
DM
469.sp
470.ne 2
d96eb2b1 471.na
9ae529ec 472\fB\fBexpandsize\fR\fR
d96eb2b1
DM
473.ad
474.RS 20n
9ae529ec
CS
475Amount of uninitialized space within the pool or device that can be used to
476increase the total capacity of the pool. Uninitialized space consists of
477any space on an EFI labeled vdev which has not been brought online
478(i.e. zpool online -e). This space occurs when a LUN is dynamically expanded.
d96eb2b1
DM
479.RE
480
f3a7f661
GW
481.sp
482.ne 2
f3a7f661
GW
483.na
484\fB\fBfragmentation\fR\fR
485.ad
486.RS 20n
f3a7f661
GW
487The amount of fragmentation in the pool.
488.RE
489
058ac9ba
BB
490.sp
491.ne 2
058ac9ba 492.na
9ae529ec 493\fB\fBfree\fR\fR
1bd201e7
CS
494.ad
495.RS 20n
9ae529ec
CS
496The amount of free space available in the pool.
497.RE
498
499.sp
500.ne 2
501.na
502\fB\fBfreeing\fR\fR
503.ad
504.RS 20n
505After a file system or snapshot is destroyed, the space it was using is
506returned to the pool asynchronously. \fB\fBfreeing\fR\fR is the amount of
507space remaining to be reclaimed. Over time \fB\fBfreeing\fR\fR will decrease
508while \fB\fBfree\fR\fR increases.
1bd201e7
CS
509.RE
510
511.sp
512.ne 2
513.na
058ac9ba
BB
514\fB\fBhealth\fR\fR
515.ad
516.RS 20n
058ac9ba
BB
517The current health of the pool. Health can be "\fBONLINE\fR", "\fBDEGRADED\fR", "\fBFAULTED\fR", " \fBOFFLINE\fR", "\fBREMOVED\fR", or "\fBUNAVAIL\fR".
518.RE
519
520.sp
521.ne 2
058ac9ba
BB
522.na
523\fB\fBguid\fR\fR
524.ad
525.RS 20n
058ac9ba
BB
526A unique identifier for the pool.
527.RE
528
529.sp
530.ne 2
058ac9ba
BB
531.na
532\fB\fBsize\fR\fR
533.ad
534.RS 20n
058ac9ba
BB
535Total size of the storage pool.
536.RE
537
9ae529ec
CS
538.sp
539.ne 2
540.na
541\fB\fBunsupported@\fR\fIfeature_guid\fR\fR
542.ad
543.RS 20n
1567e075 544.sp
9ae529ec
CS
545Information about unsupported features that are enabled on the pool. See
546\fBzpool-features\fR(5) for details.
547.RE
548
058ac9ba
BB
549.sp
550.ne 2
058ac9ba
BB
551.na
552\fB\fBused\fR\fR
553.ad
554.RS 20n
058ac9ba
BB
555Amount of storage space used within the pool.
556.RE
557
558.sp
559.LP
9ae529ec 560The space usage properties report actual physical space available to the storage pool. The physical space can be different from the total amount of space that any contained datasets can actually use. The amount of space used in a \fBraidz\fR configuration depends on the characteristics of the data being written. In addition, \fBZFS\fR reserves some space for internal accounting that the \fBzfs\fR(8) command takes into account, but the \fBzpool\fR command does not. For non-full pools of a reasonable size, these effects should be invisible. For small pools, or pools that are close to being completely full, these discrepancies may become more noticeable.
df30f566
CK
561
562.sp
563.LP
564The following property can be set at creation time:
565.sp
566.ne 2
df30f566 567.na
8fd888ba 568\fB\fBashift\fR=\fIashift\fR\fR
df30f566
CK
569.ad
570.sp .6
571.RS 4n
8fd888ba 572Pool sector size exponent, to the power of 2 (internally referred to as "ashift"). Values from 9 to 13, inclusive, are valid; also, the special value 0 (the default) means to auto-detect using the kernel's block layer and a ZFS internal exception list. I/O operations will be aligned to the specified size boundaries. Additionally, the minimum (disk) write size will be set to the specified size, so this represents a space vs. performance trade-off. The typical case for setting this property is when performance is important and the underlying disks use 4KiB sectors but report 512B sectors to the OS (for compatibility reasons); in that case, set \fBashift=12\fR (which is 1<<12 = 4096).
df30f566
CK
573.LP
574For optimal performance, the pool sector size should be greater than or equal to the sector size of the underlying disks. Since the property cannot be changed after pool creation, if in a given pool, you \fIever\fR want to use drives that \fIreport\fR 4KiB sectors, you must set \fBashift=12\fR at pool creation time.
022f7bf6
TF
575.LP
576Keep in mind is that the \fBashift\fR is \fIvdev\fR specific and is not a \fIpool\fR global. This means that when adding new vdevs to an existing pool you may need to specify the \fBashift\fR.
df30f566
CK
577.RE
578
058ac9ba
BB
579.sp
580.LP
581The following property can be set at creation time and import time:
582.sp
583.ne 2
058ac9ba 584.na
d919da83 585\fB\fBaltroot\fR=(unset) | \fIpath\fR\fR
058ac9ba
BB
586.ad
587.sp .6
588.RS 4n
57746821 589Alternate root directory. If set, this directory is prepended to any mount points within the pool. This can be used when examining an unknown pool where the mount points cannot be trusted, or in an alternate boot environment, where the typical paths are not valid. \fBaltroot\fR is not a persistent property. It is valid only while the system is up. Setting \fBaltroot\fR defaults to using \fBcachefile\fR=none, though this may be overridden using an explicit setting.
058ac9ba
BB
590.RE
591
52dd454d
TC
592.sp
593.LP
594The following property can only be set at import time:
595.sp
596.ne 2
52dd454d 597.na
d919da83 598\fB\fBreadonly\fR=\fBoff\fR | \fBon\fR\fR
52dd454d
TC
599.ad
600.sp .6
601.RS 4n
602If set to \fBon\fR, the pool will be imported in read-only mode: Synchronous data in the intent log will not be accessible, properties of the pool can not be changed and datasets of the pool can only be mounted read-only. The \fBreadonly\fR property of its datasets will be implicitly set to \fBon\fR.
603
604It can also be specified by its column name of \fBrdonly\fR.
605
606To write to a read-only pool, a export and import of the pool is required.
607.RE
608
058ac9ba
BB
609.sp
610.LP
611The following properties can be set at creation time and import time, and later changed with the \fBzpool set\fR command:
612.sp
613.ne 2
058ac9ba 614.na
d919da83 615\fB\fBautoexpand\fR=\fBoff\fR | \fBon\fR\fR
058ac9ba
BB
616.ad
617.sp .6
618.RS 4n
619Controls automatic pool expansion when the underlying LUN is grown. If set to \fBon\fR, the pool will be resized according to the size of the expanded device. If the device is part of a mirror or \fBraidz\fR then all devices within that mirror/\fBraidz\fR group must be expanded before the new space is made available to the pool. The default behavior is \fBoff\fR. This property can also be referred to by its shortened column name, \fBexpand\fR.
620.RE
621
622.sp
623.ne 2
058ac9ba 624.na
d919da83 625\fB\fBautoreplace\fR=\fBoff\fR | \fBon\fR\fR
058ac9ba
BB
626.ad
627.sp .6
628.RS 4n
629Controls automatic device replacement. If set to "\fBoff\fR", device replacement must be initiated by the administrator by using the "\fBzpool replace\fR" command. If set to "\fBon\fR", any new device, found in the same physical location as a device that previously belonged to the pool, is automatically formatted and replaced. The default behavior is "\fBoff\fR". This property can also be referred to by its shortened column name, "replace".
630.RE
631
632.sp
633.ne 2
058ac9ba 634.na
d919da83 635\fB\fBbootfs\fR=(unset) | \fIpool\fR/\fIdataset\fR\fR
058ac9ba
BB
636.ad
637.sp .6
638.RS 4n
6a107f41 639Identifies the default bootable dataset for the root pool. This property is expected to be set mainly by the installation and upgrade programs. Not all Linux distribution boot processes use the \fBbootfs\fR property.
058ac9ba
BB
640.RE
641
642.sp
643.ne 2
058ac9ba 644.na
d919da83 645\fB\fBcachefile\fR=fBnone\fR | \fIpath\fR\fR
058ac9ba
BB
646.ad
647.sp .6
648.RS 4n
6b4e21c6 649Controls the location of where the pool configuration is cached. Discovering all pools on system startup requires a cached copy of the configuration data that is stored on the root file system. All pools in this cache are automatically imported when the system boots. Some environments, such as install and clustering, need to cache this information in a different location so that pools are not automatically imported. Setting this property caches the pool configuration in a different location that can later be imported with "\fBzpool import -c\fR". Setting it to the special value "\fBnone\fR" creates a temporary pool that is never cached, and the special value \fB\&''\fR (empty string) uses the default location.
058ac9ba
BB
650.sp
651Multiple pools can share the same cache file. Because the kernel destroys and recreates this file when pools are added and removed, care should be taken when attempting to access this file. When the last pool using a \fBcachefile\fR is exported or destroyed, the file is removed.
652.RE
653
9ae529ec
CS
654.sp
655.ne 2
9ae529ec 656.na
d919da83 657\fB\fBcomment\fR=(unset) | \fB\fItext\fR\fR
9ae529ec
CS
658.ad
659.sp .6
660.RS 4n
661A text string consisting of printable ASCII characters that will be stored such that it is available even if the pool becomes faulted. An administrator can provide additional information about a pool using this property.
662.RE
663
b1d13a60
TC
664.sp
665.ne 2
b1d13a60
TC
666.na
667\fB\fBdedupditto\fR=\fB\fInumber\fR\fR
668.ad
669.sp .6
670.RS 4n
8c5edae9 671Threshold for the number of block ditto copies. If the reference count for a deduplicated block increases above this number, a new ditto copy of this block is automatically stored. The default setting is 0 which causes no ditto copies to be created for deduplicated blocks. The minimum valid nonzero setting is 100.
b1d13a60
TC
672.RE
673
058ac9ba
BB
674.sp
675.ne 2
058ac9ba
BB
676.na
677\fB\fBdelegation\fR=\fBon\fR | \fBoff\fR\fR
678.ad
679.sp .6
680.RS 4n
2d1b7b0b 681Controls whether a non-privileged user is granted access based on the dataset permissions defined on the dataset. See \fBzfs\fR(8) for more information on \fBZFS\fR delegated administration.
058ac9ba
BB
682.RE
683
684.sp
685.ne 2
058ac9ba
BB
686.na
687\fB\fBfailmode\fR=\fBwait\fR | \fBcontinue\fR | \fBpanic\fR\fR
688.ad
689.sp .6
690.RS 4n
691Controls the system behavior in the event of catastrophic pool failure. This condition is typically a result of a loss of connectivity to the underlying storage device(s) or a failure of all devices within the pool. The behavior of such an event is determined as follows:
692.sp
693.ne 2
058ac9ba
BB
694.na
695\fB\fBwait\fR\fR
696.ad
697.RS 12n
058ac9ba
BB
698Blocks all \fBI/O\fR access until the device connectivity is recovered and the errors are cleared. This is the default behavior.
699.RE
700
701.sp
702.ne 2
058ac9ba
BB
703.na
704\fB\fBcontinue\fR\fR
705.ad
706.RS 12n
058ac9ba
BB
707Returns \fBEIO\fR to any new write \fBI/O\fR requests but allows reads to any of the remaining healthy devices. Any write requests that have yet to be committed to disk would be blocked.
708.RE
709
710.sp
711.ne 2
058ac9ba
BB
712.na
713\fB\fBpanic\fR\fR
714.ad
715.RS 12n
058ac9ba
BB
716Prints out a message to the console and generates a system crash dump.
717.RE
718
719.RE
720
9ae529ec
CS
721.sp
722.ne 2
723.na
724\fB\fBfeature@\fR\fIfeature_name\fR=\fBenabled\fR\fR
725.ad
726.RS 4n
727The value of this property is the current state of \fIfeature_name\fR. The
728only valid value when setting this property is \fBenabled\fR which moves
729\fIfeature_name\fR to the enabled state. See \fBzpool-features\fR(5) for
730details on feature states.
731.RE
732
058ac9ba
BB
733.sp
734.ne 2
058ac9ba 735.na
8fd888ba 736\fB\fBlistsnapshots\fR=on | off\fR
058ac9ba
BB
737.ad
738.sp .6
739.RS 4n
740Controls whether information about snapshots associated with this pool is output when "\fBzfs list\fR" is run without the \fB-t\fR option. The default value is "off".
8fd888ba
RL
741.sp
742This property can also be referred to by its shortened name, \fBlistsnaps\fR.
058ac9ba
BB
743.RE
744
745.sp
746.ne 2
058ac9ba 747.na
d919da83 748\fB\fBversion\fR=(unset) | \fIversion\fR\fR
058ac9ba
BB
749.ad
750.sp .6
751.RS 4n
9ae529ec 752The current on-disk version of the pool. This can be increased, but never decreased. The preferred method of updating pools is with the "\fBzpool upgrade\fR" command, though this property can be used when a specific version is needed for backwards compatibility. Once feature flags are enabled on a pool this property will no longer have a value.
058ac9ba
BB
753.RE
754
755.SS "Subcommands"
756.sp
757.LP
758All subcommands that modify state are logged persistently to the pool in their original form.
759.sp
760.LP
761The \fBzpool\fR command provides subcommands to create and destroy storage pools, add capacity to storage pools, and provide information about the storage pools. The following subcommands are supported:
762.sp
763.ne 2
058ac9ba
BB
764.na
765\fB\fBzpool\fR \fB-?\fR\fR
766.ad
767.sp .6
768.RS 4n
769Displays a help message.
770.RE
771
772.sp
773.ne 2
058ac9ba 774.na
a77f29f9 775\fB\fBzpool add\fR [\fB-fgLnP\fR] [\fB-o\fR \fIproperty=value\fR] \fIpool\fR \fIvdev\fR ...\fR
058ac9ba
BB
776.ad
777.sp .6
778.RS 4n
779Adds the specified virtual devices to the given pool. The \fIvdev\fR specification is described in the "Virtual Devices" section. The behavior of the \fB-f\fR option, and the device checks performed are described in the "zpool create" subcommand.
780.sp
781.ne 2
058ac9ba
BB
782.na
783\fB\fB-f\fR\fR
784.ad
785.RS 6n
058ac9ba
BB
786Forces use of \fBvdev\fRs, even if they appear in use or specify a conflicting replication level. Not all devices can be overridden in this manner.
787.RE
788
d2f3e292
RY
789.sp
790.ne 2
d2f3e292
RY
791.na
792\fB\fB-g\fR\fR
793.ad
794.RS 6n
d2f3e292
RY
795Display vdev GUIDs instead of the normal device names. These GUIDs can be used in place of device names for the zpool detach/offline/remove/replace commands.
796.RE
797
798.sp
799.ne 2
d2f3e292
RY
800.na
801\fB\fB-L\fR\fR
802.ad
803.RS 6n
d2f3e292
RY
804Display real paths for vdevs resolving all symbolic links. This can be used to look up the current block device name regardless of the /dev/disk/ path used to open it.
805.RE
806
058ac9ba
BB
807.sp
808.ne 2
058ac9ba
BB
809.na
810\fB\fB-n\fR\fR
811.ad
812.RS 6n
058ac9ba
BB
813Displays the configuration that would be used without actually adding the \fBvdev\fRs. The actual pool creation can still fail due to insufficient privileges or device sharing.
814.RE
815
d2f3e292
RY
816.sp
817.ne 2
d2f3e292 818.na
a77f29f9 819\fB\fB-P\fR\fR
d2f3e292
RY
820.ad
821.RS 6n
d2f3e292
RY
822Display full paths for vdevs instead of only the last component of the path. This can be used in conjunction with the \fB-L\fR flag.
823.RE
824
df831108
CP
825.sp
826.ne 2
df831108
CP
827.na
828\fB\fB-o\fR \fIproperty=value\fR
829.ad
830.sp .6
831.RS 4n
022f7bf6 832Sets the given pool properties. See the "Properties" section for a list of valid properties that can be set. The only property supported at the moment is \fBashift\fR. \fBDo note\fR that some properties (among them \fBashift\fR) are \fInot\fR inherited from a previous vdev. They are vdev specific, not pool specific.
df831108
CP
833.RE
834
058ac9ba
BB
835Do not add a disk that is currently configured as a quorum device to a zpool. After a disk is in the pool, that disk can then be configured as a quorum device.
836.RE
837
838.sp
839.ne 2
058ac9ba 840.na
df831108 841\fB\fBzpool attach\fR [\fB-f\fR] [\fB-o\fR \fIproperty=value\fR] \fIpool\fR \fIdevice\fR \fInew_device\fR\fR
058ac9ba
BB
842.ad
843.sp .6
844.RS 4n
845Attaches \fInew_device\fR to an existing \fBzpool\fR device. The existing device cannot be part of a \fBraidz\fR configuration. If \fIdevice\fR is not currently part of a mirrored configuration, \fIdevice\fR automatically transforms into a two-way mirror of \fIdevice\fR and \fInew_device\fR. If \fIdevice\fR is part of a two-way mirror, attaching \fInew_device\fR creates a three-way mirror, and so on. In either case, \fInew_device\fR begins to resilver immediately.
846.sp
847.ne 2
058ac9ba
BB
848.na
849\fB\fB-f\fR\fR
850.ad
851.RS 6n
058ac9ba
BB
852Forces use of \fInew_device\fR, even if its appears to be in use. Not all devices can be overridden in this manner.
853.RE
854
df831108
CP
855.sp
856.ne 2
df831108
CP
857.na
858\fB\fB-o\fR \fIproperty=value\fR
859.ad
860.sp .6
861.RS 4n
862Sets the given pool properties. See the "Properties" section for a list of valid properties that can be set. The only property supported at the moment is "ashift".
863.RE
864
058ac9ba
BB
865.RE
866
867.sp
868.ne 2
058ac9ba
BB
869.na
870\fB\fBzpool clear\fR \fIpool\fR [\fIdevice\fR] ...\fR
871.ad
872.sp .6
873.RS 4n
874Clears device errors in a pool. If no arguments are specified, all device errors within the pool are cleared. If one or more devices is specified, only those errors associated with the specified device or devices are cleared.
875.RE
876
877.sp
878.ne 2
058ac9ba 879.na
83e9986f 880\fB\fBzpool create\fR [\fB-fnd\fR] [\fB-o\fR \fIproperty=value\fR] ... [\fB-O\fR \fIfile-system-property=value\fR] ... [\fB-m\fR \fImountpoint\fR] [\fB-R\fR \fIroot\fR] [\fB-t\fR \fItname\fR] \fIpool\fR \fIvdev\fR ...\fR
058ac9ba
BB
881.ad
882.sp .6
883.RS 4n
e6101ea8 884Creates 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 ("_"), dash ("-"), period ("."), colon (":"), and space (" "). The pool names "mirror", "raidz", "spare" and "log" are reserved, as are names beginning with the pattern "c[0-9]". The \fBvdev\fR specification is described in the "Virtual Devices" section.
058ac9ba
BB
885.sp
886The command verifies that each device specified is accessible and not currently in use by another subsystem. 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 \fBZFS\fR. Other uses, such as having a preexisting \fBUFS\fR file system, can be overridden with the \fB-f\fR option.
887.sp
888The 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 \fB-f\fR is specified. The use of differently sized devices within a single \fBraidz\fR or mirror group is also flagged as an error unless \fB-f\fR is specified.
889.sp
890Unless the \fB-R\fR option is specified, the default mount point is "/\fIpool\fR". The mount point must not exist or must be empty, or else the root dataset cannot be mounted. This can be overridden with the \fB-m\fR option.
891.sp
9ae529ec
CS
892By default all supported features are enabled on the new pool unless the \fB-d\fR option is specified.
893.sp
058ac9ba 894.ne 2
058ac9ba
BB
895.na
896\fB\fB-f\fR\fR
897.ad
898.sp .6
899.RS 4n
900Forces use of \fBvdev\fRs, even if they appear in use or specify a conflicting replication level. Not all devices can be overridden in this manner.
901.RE
902
903.sp
904.ne 2
058ac9ba
BB
905.na
906\fB\fB-n\fR\fR
907.ad
908.sp .6
909.RS 4n
910Displays 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.
911.RE
912
913.sp
914.ne 2
058ac9ba 915.na
9ae529ec
CS
916\fB\fB-d\fR\fR
917.ad
918.sp .6
919.RS 4n
920Do not enable any features on the new pool. Individual features can be enabled by setting their corresponding properties to \fBenabled\fR with the \fB-o\fR option. See \fBzpool-features\fR(5) for details about feature properties.
921.RE
922
923.sp
924.ne 2
925.na
058ac9ba
BB
926\fB\fB-o\fR \fIproperty=value\fR [\fB-o\fR \fIproperty=value\fR] ...\fR
927.ad
928.sp .6
929.RS 4n
930Sets the given pool properties. See the "Properties" section for a list of valid properties that can be set.
931.RE
932
933.sp
934.ne 2
058ac9ba
BB
935.na
936\fB\fB-O\fR \fIfile-system-property=value\fR\fR
937.ad
938.br
939.na
940\fB[\fB-O\fR \fIfile-system-property=value\fR] ...\fR
941.ad
942.sp .6
943.RS 4n
2d1b7b0b 944Sets the given file system properties in the root file system of the pool. See the "Properties" section of \fBzfs\fR(8) for a list of valid properties that can be set.
058ac9ba
BB
945.RE
946
947.sp
948.ne 2
058ac9ba
BB
949.na
950\fB\fB-R\fR \fIroot\fR\fR
951.ad
952.sp .6
953.RS 4n
954Equivalent to "-o cachefile=none,altroot=\fIroot\fR"
955.RE
956
957.sp
958.ne 2
058ac9ba
BB
959.na
960\fB\fB-m\fR \fImountpoint\fR\fR
961.ad
962.sp .6
963.RS 4n
2d1b7b0b 964Sets the mount point for the root dataset. The default mount point is "/\fIpool\fR" or "\fBaltroot\fR/\fIpool\fR" if \fBaltroot\fR is specified. The mount point must be an absolute path, "\fBlegacy\fR", or "\fBnone\fR". For more information on dataset mount points, see \fBzfs\fR(8).
058ac9ba
BB
965.RE
966
83e9986f
RY
967.sp
968.ne 2
83e9986f
RY
969.na
970\fB\fB-t\fR \fItname\fR\fR
971.ad
972.sp .6
973.RS 4n
974Sets the in-core pool name to "\fBtname\fR" while the on-disk name will be the name specified as the pool name "\fBpool\fR". 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.
975.RE
976
058ac9ba
BB
977.RE
978
979.sp
980.ne 2
058ac9ba
BB
981.na
982\fB\fBzpool destroy\fR [\fB-f\fR] \fIpool\fR\fR
983.ad
984.sp .6
985.RS 4n
986Destroys the given pool, freeing up any devices for other use. This command tries to unmount any active datasets before destroying the pool.
987.sp
988.ne 2
058ac9ba
BB
989.na
990\fB\fB-f\fR\fR
991.ad
992.RS 6n
058ac9ba
BB
993Forces any active datasets contained within the pool to be unmounted.
994.RE
995
996.RE
997
998.sp
999.ne 2
058ac9ba
BB
1000.na
1001\fB\fBzpool detach\fR \fIpool\fR \fIdevice\fR\fR
1002.ad
1003.sp .6
1004.RS 4n
65ee05ac 1005Detaches \fIdevice\fR from a mirror. The operation is refused if there are no other valid replicas of the data. If \fIdevice\fR may be re-added to the pool later on then consider the "\fBzpool offline\fR" command instead.
058ac9ba
BB
1006.RE
1007
859735c0
TF
1008.RE
1009
d050c627
TF
1010.sp
1011.ne 2
d050c627
TF
1012.na
1013\fBzpool events\fR [\fB-vHfc\fR] [\fIpool\fR] ...
1014.ad
1015.sp .6
1016.RS 4n
1017Description of the different events generated by the ZFS kernel modules. See \fBzfs-events\fR(5) for more information about the subclasses and event payloads that can be generated.
1018
1019.sp
1020.ne 2
d050c627
TF
1021.na
1022\fB\fB-v\fR\fR
1023.ad
1024.RS 6n
d050c627
TF
1025Get a full detail of the events and what information is available about it.
1026.RE
1027
1028.sp
1029.ne 2
d050c627
TF
1030.na
1031\fB\fB-H\fR\fR
1032.ad
1033.RS 6n
d050c627
TF
1034Scripted mode. Do not display headers, and separate fields by a single tab instead of arbitrary space.
1035.RE
1036
1037.sp
1038.ne 2
d050c627
TF
1039.na
1040\fB\fB-f\fR\fR
1041.ad
1042.RS 6n
d050c627
TF
1043Follow mode.
1044.RE
1045
1046.sp
1047.ne 2
d050c627
TF
1048.na
1049\fB\fB-c\fR\fR
1050.ad
1051.RS 6n
d050c627
TF
1052Clear all previous events.
1053.RE
1054
1055.RE
1056
058ac9ba
BB
1057.sp
1058.ne 2
058ac9ba 1059.na
859735c0 1060\fB\fBzpool export\fR [\fB-a\fR] [\fB-f\fR] \fIpool\fR ...\fR
058ac9ba
BB
1061.ad
1062.sp .6
1063.RS 4n
1064Exports the given pools from the system. All devices are marked as exported, but are still considered in use by other subsystems. The devices can be moved between systems (even those of different endianness) and imported as long as a sufficient number of devices are present.
1065.sp
1066Before exporting the pool, all datasets within the pool are unmounted. A pool can not be exported if it has a shared spare that is currently being used.
1067.sp
25d4782b 1068For pools to be portable, you must give the \fBzpool\fR command whole disks, not just partitions, so that \fBZFS\fR can label the disks with portable \fBEFI\fR labels. Otherwise, disk drivers on platforms of different endianness will not recognize the disks.
859735c0
TF
1069.sp
1070.ne 2
859735c0
TF
1071.na
1072\fB\fB-a\fR\fR
1073.ad
1074.RS 6n
859735c0
TF
1075Exports all pools imported on the system.
1076.RE
1077
058ac9ba
BB
1078.sp
1079.ne 2
058ac9ba
BB
1080.na
1081\fB\fB-f\fR\fR
1082.ad
1083.RS 6n
058ac9ba
BB
1084Forcefully unmount all datasets, using the "\fBunmount -f\fR" command.
1085.sp
1086This command will forcefully export the pool even if it has a shared spare that is currently being used. This may lead to potential data corruption.
1087.RE
1088
1089.RE
1090
1091.sp
1092.ne 2
058ac9ba 1093.na
2a8b84b7
AS
1094\fB\fBzpool get\fR [\fB-Hp\fR] [\fB-o \fR\fIfield\fR[,...]] "\fIall\fR" | \fIproperty\fR[,...]
1095\fIpool\fR ...\fR
058ac9ba
BB
1096.ad
1097.sp .6
1098.RS 4n
1099Retrieves the given list of properties (or all properties if "\fBall\fR" is used) for the specified storage pool(s). These properties are displayed with the following fields:
1100.sp
1101.in +2
1102.nf
2a8b84b7 1103 name Name of storage pool
058ac9ba
BB
1104 property Property name
1105 value Property value
1106 source Property source, either 'default' or 'local'.
1107.fi
1108.in -2
1109.sp
1110
1111See the "Properties" section for more information on the available pool properties.
2a8b84b7 1112
d65e7381
RE
1113.sp
1114.ne 2
d65e7381 1115.na
2a8b84b7 1116\fB\fB-H\fR\fR
d65e7381
RE
1117.ad
1118.RS 6n
2a8b84b7 1119Scripted mode. Do not display headers, and separate fields by a single tab instead of arbitrary space.
d65e7381
RE
1120.RE
1121
79eb71dc
TF
1122.sp
1123.ne 2
79eb71dc 1124.na
2a8b84b7 1125\fB\fB-p\fR\fR
79eb71dc
TF
1126.ad
1127.RS 6n
3491d6eb 1128Display numbers in parsable (exact) values.
79eb71dc
TF
1129.RE
1130
2a8b84b7
AS
1131.sp
1132.ne 2
2a8b84b7
AS
1133.na
1134\fB\fB-o\fR \fIfield\fR\fR
1135.ad
1136.RS 12n
2a8b84b7
AS
1137A comma-separated list of columns to display. \fBname,property,value,source\fR
1138is the default value.
1139.RE
058ac9ba
BB
1140.RE
1141
1142.sp
1143.ne 2
058ac9ba
BB
1144.na
1145\fB\fBzpool history\fR [\fB-il\fR] [\fIpool\fR] ...\fR
1146.ad
1147.sp .6
1148.RS 4n
1149Displays the command history of the specified pools or all pools if no pool is specified.
1150.sp
1151.ne 2
058ac9ba
BB
1152.na
1153\fB\fB-i\fR\fR
1154.ad
1155.RS 6n
058ac9ba
BB
1156Displays internally logged \fBZFS\fR events in addition to user initiated events.
1157.RE
1158
1159.sp
1160.ne 2
058ac9ba
BB
1161.na
1162\fB\fB-l\fR\fR
1163.ad
1164.RS 6n
058ac9ba
BB
1165Displays log records in long format, which in addition to standard format includes, the user name, the hostname, and the zone in which the operation was performed.
1166.RE
1167
1168.RE
1169
1170.sp
1171.ne 2
058ac9ba
BB
1172.na
1173\fB\fBzpool import\fR [\fB-d\fR \fIdir\fR | \fB-c\fR \fIcachefile\fR] [\fB-D\fR]\fR
1174.ad
1175.sp .6
1176.RS 4n
6b4e21c6 1177Lists pools available to import. If the \fB-d\fR option is not specified, this command searches for devices in "/dev". The \fB-d\fR option can be specified multiple times, and all directories are searched. If the device appears to be part of an exported pool, this command displays a summary of the pool with the name of the pool, a numeric identifier, as well as the \fIvdev\fR layout and current health of the device for each device or file. Destroyed pools, pools that were previously destroyed with the "\fBzpool destroy\fR" command, are not listed unless the \fB-D\fR option is specified.
058ac9ba
BB
1178.sp
1179The numeric identifier is unique, and can be used instead of the pool name when multiple exported pools of the same name are available.
1180.sp
1181.ne 2
058ac9ba
BB
1182.na
1183\fB\fB-c\fR \fIcachefile\fR\fR
1184.ad
1185.RS 16n
058ac9ba
BB
1186Reads configuration from the given \fBcachefile\fR that was created with the "\fBcachefile\fR" pool property. This \fBcachefile\fR is used instead of searching for devices.
1187.RE
1188
1189.sp
1190.ne 2
058ac9ba
BB
1191.na
1192\fB\fB-d\fR \fIdir\fR\fR
1193.ad
1194.RS 16n
6b4e21c6 1195Searches for devices or files in \fIdir\fR. The \fB-d\fR option can be specified multiple times.
058ac9ba
BB
1196.RE
1197
1198.sp
1199.ne 2
058ac9ba
BB
1200.na
1201\fB\fB-D\fR\fR
1202.ad
1203.RS 16n
058ac9ba
BB
1204Lists destroyed pools only.
1205.RE
1206
1207.RE
1208
1209.sp
1210.ne 2
058ac9ba 1211.na
7d11e37e 1212\fB\fBzpool import\fR [\fB-o\fR \fImntopts\fR] [ \fB-o\fR \fIproperty\fR=\fIvalue\fR] ... [\fB-d\fR \fIdir\fR | \fB-c\fR \fIcachefile\fR] [\fB-D\fR] [\fB-f\fR] [\fB-m\fR] [\fB-N\fR] [\fB-R\fR \fIroot\fR] [\fB-F\fR [\fB-n\fR]] [\fB-s\fR] \fB-a\fR\fR
058ac9ba
BB
1213.ad
1214.sp .6
1215.RS 4n
1216Imports all pools found in the search directories. Identical to the previous command, except that all pools with a sufficient number of devices available are imported. Destroyed pools, pools that were previously destroyed with the "\fBzpool destroy\fR" command, will not be imported unless the \fB-D\fR option is specified.
1217.sp
1218.ne 2
058ac9ba
BB
1219.na
1220\fB\fB-o\fR \fImntopts\fR\fR
1221.ad
1222.RS 21n
2d1b7b0b 1223Comma-separated list of mount options to use when mounting datasets within the pool. See \fBzfs\fR(8) for a description of dataset properties and mount options.
058ac9ba
BB
1224.RE
1225
1226.sp
1227.ne 2
058ac9ba
BB
1228.na
1229\fB\fB-o\fR \fIproperty=value\fR\fR
1230.ad
1231.RS 21n
058ac9ba
BB
1232Sets the specified property on the imported pool. See the "Properties" section for more information on the available pool properties.
1233.RE
1234
1235.sp
1236.ne 2
058ac9ba
BB
1237.na
1238\fB\fB-c\fR \fIcachefile\fR\fR
1239.ad
1240.RS 21n
058ac9ba
BB
1241Reads configuration from the given \fBcachefile\fR that was created with the "\fBcachefile\fR" pool property. This \fBcachefile\fR is used instead of searching for devices.
1242.RE
1243
1244.sp
1245.ne 2
058ac9ba
BB
1246.na
1247\fB\fB-d\fR \fIdir\fR\fR
1248.ad
1249.RS 21n
058ac9ba
BB
1250Searches for devices or files in \fIdir\fR. The \fB-d\fR option can be specified multiple times. This option is incompatible with the \fB-c\fR option.
1251.RE
1252
1253.sp
1254.ne 2
058ac9ba
BB
1255.na
1256\fB\fB-D\fR\fR
1257.ad
1258.RS 21n
058ac9ba
BB
1259Imports destroyed pools only. The \fB-f\fR option is also required.
1260.RE
1261
1262.sp
1263.ne 2
058ac9ba
BB
1264.na
1265\fB\fB-f\fR\fR
1266.ad
1267.RS 21n
058ac9ba
BB
1268Forces import, even if the pool appears to be potentially active.
1269.RE
1270
7f9d9946
BB
1271.sp
1272.ne 2
7f9d9946
BB
1273.na
1274\fB\fB-F\fR\fR
1275.ad
1276.RS 21n
1277Recovery mode for a non-importable pool. Attempt to return the pool to an importable state by discarding the last few transactions. Not all damaged pools can be recovered by using this option. If successful, the data from the discarded transactions is irretrievably lost. This option is ignored if the pool is importable or already imported.
1278.RE
1279
058ac9ba
BB
1280.sp
1281.ne 2
058ac9ba
BB
1282.na
1283\fB\fB-a\fR\fR
1284.ad
1285.RS 21n
6b4e21c6 1286Searches for and imports all pools found.
058ac9ba
BB
1287.RE
1288
7f9d9946
BB
1289.sp
1290.ne 2
7f9d9946
BB
1291.na
1292\fB\fB-m\fR\fR
1293.ad
1294.RS 21n
1295Allows a pool to import when there is a missing log device.
1296.RE
1297
058ac9ba
BB
1298.sp
1299.ne 2
058ac9ba
BB
1300.na
1301\fB\fB-R\fR \fIroot\fR\fR
1302.ad
1303.RS 21n
058ac9ba
BB
1304Sets the "\fBcachefile\fR" property to "\fBnone\fR" and the "\fIaltroot\fR" property to "\fIroot\fR".
1305.RE
1306
7f9d9946
BB
1307.sp
1308.ne 2
7f9d9946
BB
1309.na
1310\fB\fB-N\fR\fR
1311.ad
1312.RS 21n
1313Import the pool without mounting any file systems.
1314.RE
1315
1316.sp
1317.ne 2
7f9d9946
BB
1318.na
1319\fB\fB-n\fR\fR
1320.ad
1321.RS 21n
1322Used with the \fB-F\fR recovery option. Determines whether a non-importable pool can be made importable again, but does not actually perform the pool recovery. For more details about pool recovery mode, see the \fB-F\fR option, above.
1323.RE
1324
21b446a7
TF
1325.sp
1326.ne 2
21b446a7
TF
1327.na
1328\fB\fB-X\fR\fR
1329.ad
1330.RS 21n
1331Used with the \fB-F\fR recovery option. Determines whether extreme measures to find a valid txg should take place. This allows the pool to be rolled back to a txg which is no longer guaranteed to be consistent. Pools imported at an inconsistent txg may contain uncorrectable checksum errors. For more details about pool recovery mode, see the \fB-F\fR option, above.
1332\fBWARNING\fR: This option can be extremely hazardous to the health of your pool and should only be used as a last resort.
1333.RE
1334
1335.sp
1336.ne 2
21b446a7
TF
1337.na
1338\fB\fB-T\fR\fR
1339.ad
1340.RS 21n
1341Specify the txg to use for rollback. Implies \fB-FX\fR. For more details about pool recovery mode, see the \fB-X\fR option, above.
1342\fBWARNING\fR: This option can be extremely hazardous to the health of your pool and should only be used as a last resort.
1343.RE
1344
7d11e37e
BB
1345.sp
1346.ne 2
7d11e37e
BB
1347.na
1348\fB\fB-s\fR
1349.ad
1350.RS 21n
7d11e37e
BB
1351Scan using the default search path, the libblkid cache will not be consulted. A custom search path may be specified by setting the \fBZPOOL_IMPORT_PATH\fR environment variable.
1352.RE
1353
058ac9ba
BB
1354.RE
1355
1356.sp
1357.ne 2
058ac9ba 1358.na
7d11e37e 1359\fB\fBzpool import\fR [\fB-o\fR \fImntopts\fR] [ \fB-o\fR \fIproperty\fR=\fIvalue\fR] ... [\fB-d\fR \fIdir\fR | \fB-c\fR \fIcachefile\fR] [\fB-D\fR] [\fB-f\fR] [\fB-m\fR] [\fB-R\fR \fIroot\fR] [\fB-F\fR [\fB-n\fR]] [\fB-t\fR]] [\fB-s\fR] \fIpool\fR | \fIid\fR [\fInewpool\fR]\fR
058ac9ba
BB
1360.ad
1361.sp .6
1362.RS 4n
1363Imports a specific pool. A pool can be identified by its name or the numeric identifier. If \fInewpool\fR is specified, the pool is imported using the name \fInewpool\fR. Otherwise, it is imported with the same name as its exported name.
1364.sp
1365If a device is removed from a system without running "\fBzpool export\fR" first, the device appears as potentially active. It cannot be determined if this was a failed export, or whether the device is really in use from another host. To import a pool in this state, the \fB-f\fR option is required.
1366.sp
1367.ne 2
058ac9ba
BB
1368.na
1369\fB\fB-o\fR \fImntopts\fR\fR
1370.ad
1371.sp .6
1372.RS 4n
2d1b7b0b 1373Comma-separated list of mount options to use when mounting datasets within the pool. See \fBzfs\fR(8) for a description of dataset properties and mount options.
058ac9ba
BB
1374.RE
1375
1376.sp
1377.ne 2
058ac9ba
BB
1378.na
1379\fB\fB-o\fR \fIproperty=value\fR\fR
1380.ad
1381.sp .6
1382.RS 4n
1383Sets the specified property on the imported pool. See the "Properties" section for more information on the available pool properties.
1384.RE
1385
1386.sp
1387.ne 2
058ac9ba
BB
1388.na
1389\fB\fB-c\fR \fIcachefile\fR\fR
1390.ad
1391.sp .6
1392.RS 4n
1393Reads configuration from the given \fBcachefile\fR that was created with the "\fBcachefile\fR" pool property. This \fBcachefile\fR is used instead of searching for devices.
1394.RE
1395
1396.sp
1397.ne 2
058ac9ba
BB
1398.na
1399\fB\fB-d\fR \fIdir\fR\fR
1400.ad
1401.sp .6
1402.RS 4n
1403Searches for devices or files in \fIdir\fR. The \fB-d\fR option can be specified multiple times. This option is incompatible with the \fB-c\fR option.
1404.RE
1405
1406.sp
1407.ne 2
058ac9ba
BB
1408.na
1409\fB\fB-D\fR\fR
1410.ad
1411.sp .6
1412.RS 4n
1413Imports destroyed pool. The \fB-f\fR option is also required.
1414.RE
1415
1416.sp
1417.ne 2
058ac9ba
BB
1418.na
1419\fB\fB-f\fR\fR
1420.ad
1421.sp .6
1422.RS 4n
1423Forces import, even if the pool appears to be potentially active.
1424.RE
1425
7f9d9946
BB
1426.sp
1427.ne 2
7f9d9946
BB
1428.na
1429\fB\fB-F\fR\fR
1430.ad
1431.sp .6
1432.RS 4n
1433Recovery mode for a non-importable pool. Attempt to return the pool to an importable state by discarding the last few transactions. Not all damaged pools can be recovered by using this option. If successful, the data from the discarded transactions is irretrievably lost. This option is ignored if the pool is importable or already imported.
1434.RE
1435
058ac9ba
BB
1436.sp
1437.ne 2
058ac9ba
BB
1438.na
1439\fB\fB-R\fR \fIroot\fR\fR
1440.ad
1441.sp .6
1442.RS 4n
1443Sets the "\fBcachefile\fR" property to "\fBnone\fR" and the "\fIaltroot\fR" property to "\fIroot\fR".
1444.RE
1445
7f9d9946
BB
1446.sp
1447.ne 2
7f9d9946
BB
1448.na
1449\fB\fB-n\fR\fR
1450.ad
1451.sp .6
1452.RS 4n
1453Used with the \fB-F\fR recovery option. Determines whether a non-importable pool can be made importable again, but does not actually perform the pool recovery. For more details about pool recovery mode, see the \fB-F\fR option, above.
1454.RE
1455
21b446a7
TF
1456.sp
1457.ne 2
21b446a7
TF
1458.na
1459\fB\fB-X\fR\fR
1460.ad
1461.sp .6
1462.RS 4n
1463Used with the \fB-F\fR recovery option. Determines whether extreme measures to find a valid txg should take place. This allows the pool to be rolled back to a txg which is no longer guaranteed to be consistent. Pools imported at an inconsistent txg may contain uncorrectable checksum errors. For more details about pool recovery mode, see the \fB-F\fR option, above.
1464\fBWARNING\fR: This option can be extremely hazardous to the health of your pool and should only be used as a last resort.
1465.RE
1466
1467.sp
1468.ne 2
21b446a7
TF
1469.na
1470\fB\fB-T\fR\fR
1471.ad
1472.sp .6
1473.RS 4n
1474Specify the txg to use for rollback. Implies \fB-FX\fR. For more details about pool recovery mode, see the \fB-X\fR option, above.
1475\fBWARNING\fR: This option can be extremely hazardous to the health of your pool and should only be used as a last resort.
1476.RE
1477
26b42f3f
RY
1478.sp
1479.ne 2
26b42f3f
RY
1480.na
1481\fB\fB-t\fR\fR
1482.ad
1483.sp .6
1484.RS 4n
00d2a8c9 1485Used with "\fBnewpool\fR". Specifies that "\fBnewpool\fR" is temporary. Temporary pool names last until export. Ensures that the original pool name will be used in all label updates and therefore is retained upon export. Will also set -o cachefile=none when not explicitly specified.
26b42f3f
RY
1486.RE
1487
7f9d9946
BB
1488.sp
1489.ne 2
7f9d9946
BB
1490.na
1491\fB\fB-m\fR\fR
1492.ad
1493.sp .6
1494.RS 4n
1495Allows a pool to import when there is a missing log device.
1496.RE
1497
7d11e37e
BB
1498.sp
1499.ne 2
7d11e37e
BB
1500.na
1501\fB\fB-s\fR
1502.ad
1503.sp .6
1504.RS 4n
1505Scan using the default search path, the libblkid cache will not be consulted. A custom search path may be specified by setting the \fBZPOOL_IMPORT_PATH\fR environment variable.
1506.RE
1507
058ac9ba
BB
1508.RE
1509
1510.sp
1511.ne 2
058ac9ba 1512.na
193a37cb
TH
1513\fB\fBzpool iostat\fR [\fB-T\fR \fBd\fR | \fBu\fR] [\fB-ghHLpPvy\fR] [\fB-w\fR|[\fB-lq\fR]] [[\fIpool\fR ...]|[\fIpool vdev\fR ...]|[\fIvdev\fR ...]] [\fIinterval\fR[\fIcount\fR]]\fR
1514
058ac9ba
BB
1515.ad
1516.sp .6
1517.RS 4n
193a37cb
TH
1518Displays \fBI/O\fR statistics for the given \fIpool\fRs/\fIvdev\fRs. You can
1519pass in a list of \fIpool\fRs, a \fIpool\fR and list of \fIvdev\fRs in that
1520\fIpool\fR, or a list of any \fIvdev\fRs from any \fIpool\fR. If no items are
1521specified, statistics for every pool in the system are shown. When given an
1522interval, the statistics are printed every \fIinterval\fR seconds until
1523\fBCtrl-C\fR is pressed. If \fIcount\fR is specified, the command exits after
1524\fIcount\fR reports are printed. The first report printed is always the
1525statistics since boot regardless of whether \fIinterval\fR and \fIcount\fR
1526are passed. However, this behavior can be suppressed with the -y flag. Also
1527note that the units of 'K', 'M', 'G'... that are printed in the report are in
1528base 1024. To get the raw values, use the \fB-p\fR flag.
058ac9ba
BB
1529.sp
1530.ne 2
058ac9ba
BB
1531.na
1532\fB\fB-T\fR \fBu\fR | \fBd\fR\fR
1533.ad
1534.RS 12n
058ac9ba
BB
1535Display a time stamp.
1536.sp
1537Specify \fBu\fR for a printed representation of the internal representation of time. See \fBtime\fR(2). Specify \fBd\fR for standard date format. See \fBdate\fR(1).
1538.RE
1539
d2f3e292
RY
1540.sp
1541.ne 2
d2f3e292
RY
1542.na
1543\fB\fB-g\fR\fR
1544.ad
1545.RS 12n
d2f3e292
RY
1546Display vdev GUIDs instead of the normal device names. These GUIDs can be used in place of device names for the zpool detach/offline/remove/replace commands.
1547.RE
1548
193a37cb
TH
1549.sp
1550.ne 2
193a37cb
TH
1551.na
1552\fB\fB-H\fR\fR
1553.ad
1554.RS 12n
193a37cb
TH
1555Scripted mode. Do not display headers, and separate fields by a single tab instead of arbitrary space.
1556.RE
1557
d2f3e292
RY
1558.sp
1559.ne 2
d2f3e292
RY
1560.na
1561\fB\fB-L\fR\fR
1562.ad
1563.RS 12n
d2f3e292
RY
1564Display real paths for vdevs resolving all symbolic links. This can be used to look up the current block device name regardless of the /dev/disk/ path used to open it.
1565.RE
1566
193a37cb
TH
1567.sp
1568.ne 2
193a37cb
TH
1569.na
1570\fB\fB-p\fR\fR
1571.ad
1572.RS 12n
3491d6eb 1573Display numbers in parsable (exact) values. Time values are in nanoseconds.
193a37cb
TH
1574.RE
1575
d2f3e292
RY
1576.sp
1577.ne 2
d2f3e292 1578.na
a77f29f9 1579\fB\fB-P\fR\fR
d2f3e292
RY
1580.ad
1581.RS 12n
d2f3e292
RY
1582Display full paths for vdevs instead of only the last component of the path. This can be used in conjunction with the \fB-L\fR flag.
1583.RE
1584
058ac9ba
BB
1585.sp
1586.ne 2
058ac9ba
BB
1587.na
1588\fB\fB-v\fR\fR
1589.ad
1590.RS 12n
058ac9ba
BB
1591Verbose statistics. Reports usage statistics for individual \fIvdevs\fR within the pool, in addition to the pool-wide statistics.
1592.RE
1593
41092124
HM
1594.sp
1595.ne 2
41092124
HM
1596.na
1597\fB\fB-y\fR\fR
1598.ad
1599.RS 12n
41092124
HM
1600Omit statistics since boot. Normally the first line of output reports the statistics since boot. This option suppresses that first line of output.
1601.RE
193a37cb
TH
1602.sp
1603.ne 2
193a37cb
TH
1604.na
1605\fB\fB-w\fR\fR
1606.ad
1607.RS 12n
193a37cb
TH
1608Display latency histograms:
1609
1610.sp
1611.ne 2
193a37cb
TH
1612.na
1613total_wait:
1614.ad
1615.RS 20n
193a37cb
TH
1616Total IO time (queuing + disk IO time).
1617.RE
1618.ne 2
193a37cb
TH
1619.na
1620disk_wait:
1621.ad
1622.RS 20n
193a37cb
TH
1623Disk IO time (time reading/writing the disk).
1624.RE
1625.ne 2
193a37cb
TH
1626.na
1627syncq_wait:
1628.ad
1629.RS 20n
193a37cb
TH
1630Amount of time IO spent in synchronous priority queues. Does not include
1631disk time.
1632.RE
1633.ne 2
193a37cb
TH
1634.na
1635asyncq_wait:
1636.ad
1637.RS 20n
193a37cb
TH
1638Amount of time IO spent in asynchronous priority queues. Does not include
1639disk time.
1640.RE
1641.ne 2
193a37cb
TH
1642.na
1643scrub:
1644.ad
1645.RS 20n
193a37cb
TH
1646Amount of time IO spent in scrub queue. Does not include disk time.
1647
1648
1649.RE
1650
1651All histogram buckets are power-of-two sized. The time labels are the end
1652ranges of the buckets, so for example, a 15ns bucket stores latencies from
16538-15ns. The last bucket is also a catch-all for latencies higher than the
1654maximum.
1655.RE
1656.sp
1657.ne 2
193a37cb
TH
1658.na
1659\fB\fB-l\fR\fR
1660.ad
1661.RS 12n
193a37cb
TH
1662Include average latency statistics:
1663
1664.sp
1665.ne 2
193a37cb
TH
1666.na
1667total_wait:
1668.ad
1669.RS 20n
193a37cb
TH
1670Average total IO time (queuing + disk IO time).
1671.RE
1672.ne 2
193a37cb
TH
1673.na
1674disk_wait:
1675.ad
1676.RS 20n
193a37cb
TH
1677Average disk IO time (time reading/writing the disk).
1678.RE
1679.ne 2
193a37cb
TH
1680.na
1681syncq_wait:
1682.ad
1683.RS 20n
193a37cb
TH
1684Average amount of time IO spent in synchronous priority queues. Does not
1685include disk time.
1686.RE
1687.ne 2
193a37cb
TH
1688.na
1689asyncq_wait:
1690.ad
1691.RS 20n
193a37cb
TH
1692Average amount of time IO spent in asynchronous priority queues. Does not
1693include disk time.
1694.RE
1695.ne 2
193a37cb
TH
1696.na
1697scrub:
1698.ad
1699.RS 20n
193a37cb
TH
1700Average queuing time in scrub queue. Does not include disk time.
1701.RE
41092124 1702
193a37cb
TH
1703.RE
1704.sp
1705.ne 2
193a37cb
TH
1706.na
1707\fB\fB-q\fR\fR
1708.ad
1709.RS 12n
193a37cb
TH
1710Include active queue statistics. Each priority queue has both pending ("pend")
1711and active ("activ") IOs. Pending IOs are waiting to be issued to the disk, and
1712active IOs have been issued to disk and are waiting for completion. These stats
1713are broken out by priority queue:
1714.sp
1715.ne 2
193a37cb
TH
1716.na
1717syncq_read/write:
1718.ad
1719.RS 20n
193a37cb
TH
1720Current number of entries in synchronous priority queues.
1721.RE
1722.ne 2
193a37cb
TH
1723.na
1724asyncq_read/write:
1725.ad
1726.RS 20n
193a37cb
TH
1727Current number of entries in asynchronous priority queues.
1728.RE
1729.ne 2
193a37cb
TH
1730.na
1731scrubq_read:
1732.ad
1733.RS 20n
193a37cb 1734Current number of entries in scrub queue.
058ac9ba
BB
1735.RE
1736
193a37cb
TH
1737All queue statistics are instantaneous measurements of the number of entries
1738in the queues. If you specify an interval, the measurements will be sampled
1739from the end of the interval.
1740.RE
131cc95c
DK
1741.sp
1742.ne 2
131cc95c
DK
1743.na
1744\fB\fBzpool labelclear\fR [\fB-f\fR] \fIdevice\fR
1745.ad
1746.sp .6
1747.RS 4n
1748Removes ZFS label information from the specified device. The device must not be part of an active pool configuration.
1749.sp
1750.ne 2
131cc95c
DK
1751.na
1752\fB\fB-f\fR\fR
1753.ad
1754.RS 12n
131cc95c
DK
1755Treat exported or foreign devices as inactive.
1756.RE
1757
1758.RE
1759
058ac9ba
BB
1760.sp
1761.ne 2
058ac9ba 1762.na
2a8b84b7 1763\fB\fBzpool list\fR [\fB-T\fR \fBd\fR | \fBu\fR] [\fB-HgLpPv\fR] [\fB-o\fR \fIprops\fR[,...]] [\fIpool\fR] ... [\fIinterval\fR[\fIcount\fR]]\fR
058ac9ba
BB
1764.ad
1765.sp .6
1766.RS 4n
6e1b9d03 1767Lists the given pools along with a health status and space usage. If no \fIpools\fR are specified, all pools in the system are listed. When given an \fIinterval\fR, the information is printed every \fIinterval\fR seconds until \fBCtrl-C\fR is pressed. If \fIcount\fR is specified, the command exits after \fIcount\fR reports are printed.
058ac9ba
BB
1768.sp
1769.ne 2
058ac9ba
BB
1770.na
1771\fB\fB-H\fR\fR
1772.ad
1773.RS 12n
058ac9ba
BB
1774Scripted mode. Do not display headers, and separate fields by a single tab instead of arbitrary space.
1775.RE
1776
d2f3e292
RY
1777.sp
1778.ne 2
d2f3e292
RY
1779.na
1780\fB\fB-g\fR\fR
1781.ad
1782.RS 12n
d2f3e292
RY
1783Display vdev GUIDs instead of the normal device names. These GUIDs can be used in place of device names for the zpool detach/offline/remove/replace commands.
1784.RE
1785
1786.sp
1787.ne 2
d2f3e292
RY
1788.na
1789\fB\fB-L\fR\fR
1790.ad
1791.RS 12n
d2f3e292
RY
1792Display real paths for vdevs resolving all symbolic links. This can be used to look up the current block device name regardless of the /dev/disk/ path used to open it.
1793.RE
1794
2a8b84b7
AS
1795.sp
1796.ne 2
2a8b84b7
AS
1797.na
1798\fB\fB-p\fR\fR
1799.ad
1800.RS 12n
2a8b84b7
AS
1801Display numbers in parsable (exact) values.
1802.RE
1803
d2f3e292
RY
1804.sp
1805.ne 2
d2f3e292 1806.na
a77f29f9 1807\fB\fB-P\fR\fR
d2f3e292
RY
1808.ad
1809.RS 12n
d2f3e292
RY
1810Display full paths for vdevs instead of only the last component of the path. This can be used in conjunction with the \fB-L\fR flag.
1811.RE
1812
2a8b84b7 1813.sp
6e1b9d03 1814.ne 2
6e1b9d03 1815.na
2e2ddc30 1816\fB\fB-T\fR \fBd\fR | \fBu\fR\fR
6e1b9d03
CE
1817.ad
1818.RS 12n
6e1b9d03
CE
1819Display a time stamp.
1820.sp
1821Specify \fBu\fR for a printed representation of the internal representation of time. See \fBtime\fR(2). Specify \fBd\fR for standard date format. See \fBdate\fR(1).
1822.RE
1823
058ac9ba
BB
1824.sp
1825.ne 2
058ac9ba
BB
1826.na
1827\fB\fB-o\fR \fIprops\fR\fR
1828.ad
1829.RS 12n
f3a7f661 1830Comma-separated list of properties to display. See the "Properties" section for a list of valid properties. The default list is "name, size, used, available, fragmentation, expandsize, capacity, dedupratio, health, altroot"
1bd201e7
CS
1831.RE
1832
1833.sp
1834.ne 2
1bd201e7
CS
1835.na
1836\fB\fB-v\fR\fR
1837.ad
1838.RS 12n
1bd201e7 1839Verbose statistics. Reports usage statistics for individual \fIvdevs\fR within the pool, in addition to the pool-wise statistics.
058ac9ba
BB
1840.RE
1841
1842.RE
1843
1844.sp
1845.ne 2
058ac9ba
BB
1846.na
1847\fB\fBzpool offline\fR [\fB-t\fR] \fIpool\fR \fIdevice\fR ...\fR
1848.ad
1849.sp .6
1850.RS 4n
1851Takes the specified physical device offline. While the \fIdevice\fR is offline, no attempt is made to read or write to the device.
1852.sp
1853This command is not applicable to spares or cache devices.
1854.sp
1855.ne 2
058ac9ba
BB
1856.na
1857\fB\fB-t\fR\fR
1858.ad
1859.RS 6n
058ac9ba
BB
1860Temporary. Upon reboot, the specified physical device reverts to its previous state.
1861.RE
1862
1863.RE
1864
1865.sp
1866.ne 2
058ac9ba
BB
1867.na
1868\fB\fBzpool online\fR [\fB-e\fR] \fIpool\fR \fIdevice\fR...\fR
1869.ad
1870.sp .6
1871.RS 4n
1872Brings the specified physical device online.
1873.sp
1874This command is not applicable to spares or cache devices.
1875.sp
1876.ne 2
058ac9ba
BB
1877.na
1878\fB\fB-e\fR\fR
1879.ad
1880.RS 6n
058ac9ba
BB
1881Expand the device to use all available space. If the device is part of a mirror or \fBraidz\fR then all devices must be expanded before the new space will become available to the pool.
1882.RE
1883
1884.RE
1885
1886.sp
1887.ne 2
058ac9ba 1888.na
3541dc6d
GA
1889\fB\fBzpool reguid\fR \fIpool\fR
1890.ad
1891.sp .6
1892.RS 4n
5853fe79
GW
1893Generates a new unique identifier for the pool. You must ensure that all
1894devices in this pool are online and healthy before performing this action.
1895.RE
1896
1897.sp
1898.ne 2
1899.na
1900\fB\fBzpool reopen\fR \fIpool\fR
1901.ad
1902.sp .6
1903.RS 4n
1904Reopen all the vdevs associated with the pool.
3541dc6d
GA
1905.RE
1906
1907.sp
1908.ne 2
1909.na
058ac9ba
BB
1910\fB\fBzpool remove\fR \fIpool\fR \fIdevice\fR ...\fR
1911.ad
1912.sp .6
1913.RS 4n
1914Removes the specified device from the pool. This command currently only supports removing hot spares, cache, and log devices. A mirrored log device can be removed by specifying the top-level mirror for the log. Non-log devices that are part of a mirrored configuration can be removed using the \fBzpool detach\fR command. Non-redundant and \fBraidz\fR devices cannot be removed from a pool.
1915.RE
1916
1917.sp
1918.ne 2
058ac9ba 1919.na
628668a3 1920\fB\fBzpool replace\fR [\fB-f\fR] [\fB-o\fR \fIproperty=value\fR] \fIpool\fR \fIold_device\fR [\fInew_device\fR]\fR
058ac9ba
BB
1921.ad
1922.sp .6
1923.RS 4n
1924Replaces \fIold_device\fR with \fInew_device\fR. This is equivalent to attaching \fInew_device\fR, waiting for it to resilver, and then detaching \fIold_device\fR.
1925.sp
1926The size of \fInew_device\fR must be greater than or equal to the minimum size of all the devices in a mirror or \fBraidz\fR configuration.
1927.sp
1fe2e237 1928\fInew_device\fR is required if the pool is not redundant. If \fInew_device\fR is not specified, it defaults to \fIold_device\fR. This form of replacement is useful after an existing disk has failed and has been physically replaced. In this case, the new disk may have the same \fB/dev\fR path as the old device, even though it is actually a different disk. \fBZFS\fR recognizes this.
058ac9ba
BB
1929.sp
1930.ne 2
058ac9ba
BB
1931.na
1932\fB\fB-f\fR\fR
1933.ad
1934.RS 6n
058ac9ba
BB
1935Forces use of \fInew_device\fR, even if its appears to be in use. Not all devices can be overridden in this manner.
1936.RE
1937
628668a3
TF
1938.sp
1939.ne 2
628668a3
TF
1940.na
1941\fB\fB-o\fR \fIproperty=value\fR
1942.ad
1943.sp .6n
1944.RS 6n
1945Sets the given pool properties. See the "Properties" section for a list of valid properties that can be set. The only property supported at the moment is \fBashift\fR. \fBDo note\fR that some properties (among them \fBashift\fR) are \fInot\fR inherited from a previous vdev. They are vdev specific, not pool specific.
1946.RE
1947
058ac9ba
BB
1948.RE
1949
1950.sp
1951.ne 2
058ac9ba
BB
1952.na
1953\fB\fBzpool scrub\fR [\fB-s\fR] \fIpool\fR ...\fR
1954.ad
1955.sp .6
1956.RS 4n
1957Begins a scrub. The scrub examines all data in the specified pools to verify that it checksums correctly. For replicated (mirror or \fBraidz\fR) devices, \fBZFS\fR automatically repairs any damage discovered during the scrub. The "\fBzpool status\fR" command reports the progress of the scrub and summarizes the results of the scrub upon completion.
1958.sp
1959Scrubbing and resilvering are very similar operations. The difference is that resilvering only examines data that \fBZFS\fR knows to be out of date (for example, when attaching a new device to a mirror or replacing an existing device), whereas scrubbing examines all data to discover silent errors due to hardware faults or disk failure.
1960.sp
1961Because scrubbing and resilvering are \fBI/O\fR-intensive operations, \fBZFS\fR only allows one at a time. If a scrub is already in progress, the "\fBzpool scrub\fR" command terminates it and starts a new scrub. If a resilver is in progress, \fBZFS\fR does not allow a scrub to be started until the resilver completes.
1962.sp
1963.ne 2
058ac9ba
BB
1964.na
1965\fB\fB-s\fR\fR
1966.ad
1967.RS 6n
058ac9ba
BB
1968Stop scrubbing.
1969.RE
1970
1971.RE
1972
1973.sp
1974.ne 2
058ac9ba
BB
1975.na
1976\fB\fBzpool set\fR \fIproperty\fR=\fIvalue\fR \fIpool\fR\fR
1977.ad
1978.sp .6
1979.RS 4n
1980Sets the given property on the specified pool. See the "Properties" section for more information on what properties can be set and acceptable values.
1981.RE
1982
fb827006
SB
1983.sp
1984.ne 2
fb827006 1985.na
a77f29f9 1986\fBzpool split\fR [\fB-gLnP\fR] [\fB-R\fR \fIaltroot\fR] [\fB-o\fR \fIproperty=value\fR] \fIpool\fR \fInewpool\fR [\fIdevice\fR ...]
fb827006
SB
1987.ad
1988.sp .6
1989.RS 4n
52e68edc
TC
1990Split devices off \fIpool\fR creating \fInewpool\fR. All \fBvdev\fRs in \fIpool\fR must be mirrors and the pool must not be in the process of resilvering. At the time of the split, \fInewpool\fR will be a replica of \fIpool\fR. By default, the last device in each mirror is split from \fIpool\fR to create \fInewpool\fR.
1991
1992The optional \fIdevice\fR specification causes the specified device(s) to be included in the new pool and, should any devices remain unspecified, the last device in each mirror is used as would be by default.
fb827006 1993
d2f3e292
RY
1994.sp
1995.ne 2
d2f3e292
RY
1996.na
1997\fB\fB-g\fR\fR
1998.ad
1999.RS 6n
d2f3e292
RY
2000Display vdev GUIDs instead of the normal device names. These GUIDs can be used in place of device names for the zpool detach/offline/remove/replace commands.
2001.RE
2002
2003.sp
2004.ne 2
d2f3e292
RY
2005.na
2006\fB\fB-L\fR\fR
2007.ad
2008.RS 6n
d2f3e292
RY
2009Display real paths for vdevs resolving all symbolic links. This can be used to look up the current block device name regardless of the /dev/disk/ path used to open it.
2010.RE
2011
fb827006
SB
2012.sp
2013.ne 2
fb827006
SB
2014.na
2015\fB\fB-n\fR \fR
2016.ad
2017.sp .6
2018.RS 4n
2019Do dry run, do not actually perform the split. Print out the expected configuration of \fInewpool\fR.
2020.RE
2021
d2f3e292
RY
2022.sp
2023.ne 2
d2f3e292 2024.na
a77f29f9 2025\fB\fB-P\fR\fR
d2f3e292
RY
2026.ad
2027.RS 6n
d2f3e292
RY
2028Display full paths for vdevs instead of only the last component of the path. This can be used in conjunction with the \fB-L\fR flag.
2029.RE
2030
fb827006
SB
2031.sp
2032.ne 2
fb827006
SB
2033.na
2034\fB\fB-R\fR \fIaltroot\fR \fR
2035.ad
2036.sp .6
2037.RS 4n
6b4e21c6 2038Set \fIaltroot\fR for \fInewpool\fR and automatically import it. This can be useful to avoid mountpoint collisions if \fInewpool\fR is imported on the same filesystem as \fIpool\fR.
fb827006
SB
2039.RE
2040
2041.sp
2042.ne 2
fb827006
SB
2043.na
2044\fB\fB-o\fR \fIproperty=value\fR \fR
2045.ad
2046.sp .6
2047.RS 4n
2048Sets the specified property for \fInewpool\fR. See the “Properties” section for more information on the available pool properties.
2049.RE
2050
2051.RE
2052
058ac9ba
BB
2053.sp
2054.ne 2
058ac9ba 2055.na
a77f29f9 2056\fBzpool status\fR [\fB-gLPvxD\fR] [\fB-T\fR d | u] [\fIpool\fR] ... [\fIinterval\fR [\fIcount\fR]]
058ac9ba
BB
2057.ad
2058.sp .6
2059.RS 4n
2060Displays the detailed health status for the given pools. If no \fIpool\fR is specified, then the status of each pool in the system is displayed. For more information on pool and device health, see the "Device Failure and Recovery" section.
2061.sp
2062If a scrub or resilver is in progress, this command reports the percentage done and the estimated time to completion. Both of these are only approximate, because the amount of data in the pool and the other workloads on the system can change.
d2f3e292 2063
058ac9ba
BB
2064.sp
2065.ne 2
058ac9ba 2066.na
d2f3e292 2067\fB\fB-g\fR\fR
058ac9ba 2068.ad
2e2ddc30 2069.RS 12n
d2f3e292
RY
2070Display vdev GUIDs instead of the normal device names. These GUIDs can be used innplace of device names for the zpool detach/offline/remove/replace commands.
2071.RE
2072
2073.sp
2074.ne 2
d2f3e292
RY
2075.na
2076\fB\fB-L\fR\fR
2077.ad
2078.RS 12n
d2f3e292
RY
2079Display real paths for vdevs resolving all symbolic links. This can be used to look up the current block device name regardless of the /dev/disk/ path used to open it.
2080.RE
2081
2082.sp
2083.ne 2
d2f3e292 2084.na
a77f29f9 2085\fB\fB-P\fR\fR
d2f3e292
RY
2086.ad
2087.RS 12n
d2f3e292 2088Display full paths for vdevs instead of only the last component of the path. This can be used in conjunction with the \fB-L\fR flag.
058ac9ba
BB
2089.RE
2090
2091.sp
2092.ne 2
058ac9ba
BB
2093.na
2094\fB\fB-v\fR\fR
2095.ad
2e2ddc30 2096.RS 12n
058ac9ba
BB
2097Displays verbose data error information, printing out a complete list of all data errors since the last complete pool scrub.
2098.RE
2099
d2f3e292
RY
2100.sp
2101.ne 2
d2f3e292
RY
2102.na
2103\fB\fB-x\fR\fR
2104.ad
2105.RS 12n
d2f3e292
RY
2106Only display status for pools that are exhibiting errors or are otherwise unavailable. Warnings about pools not using the latest on-disk format will not be included.
2107.RE
2108
2e2ddc30
TC
2109.sp
2110.ne 2
2e2ddc30
TC
2111.na
2112\fB\fB-D\fR\fR
2113.ad
2114.RS 12n
2e2ddc30
TC
2115Display a histogram of deduplication statistics, showing the allocated (physically present on disk) and
2116referenced (logically referenced in the pool) block counts and sizes by reference count.
2117.RE
2118
2119.sp
2120.ne 2
2e2ddc30
TC
2121.na
2122\fB\fB-T\fR \fBd\fR | \fBu\fR\fR
2123.ad
2124.RS 12n
2e2ddc30
TC
2125Display a time stamp.
2126.sp
2127Specify \fBu\fR for a printed representation of the internal representation of time. See \fBtime\fR(2). Specify \fBd\fR for standard date format. See \fBdate\fR(1).
058ac9ba
BB
2128.RE
2129
53e03135 2130.RE
2131
058ac9ba
BB
2132.sp
2133.ne 2
058ac9ba
BB
2134.na
2135\fB\fBzpool upgrade\fR\fR
2136.ad
2137.sp .6
2138.RS 4n
b9b24bb4 2139Displays pools which do not have all supported features enabled and pools formatted using a legacy ZFS version number. These pools can continue to be used, but some features may not be available. Use "\fBzpool upgrade -a\fR" to enable all features on all pools.
058ac9ba
BB
2140.RE
2141
2142.sp
2143.ne 2
058ac9ba
BB
2144.na
2145\fB\fBzpool upgrade\fR \fB-v\fR\fR
2146.ad
2147.sp .6
2148.RS 4n
b9b24bb4 2149Displays legacy \fBZFS\fR versions supported by the current software. See \fBzfs-features\fR(5) for a description of feature flags features supported by the current software.
058ac9ba
BB
2150.RE
2151
2152.sp
2153.ne 2
058ac9ba
BB
2154.na
2155\fB\fBzpool upgrade\fR [\fB-V\fR \fIversion\fR] \fB-a\fR | \fIpool\fR ...\fR
2156.ad
2157.sp .6
2158.RS 4n
8f343973 2159Enables all supported features on the given pool. Once this is done, the pool will no longer be accessible on systems that do not support feature flags. See \fBzfs-features\fR(5) for details on compatibility with systems that support feature flags, but do not support all features enabled on the pool.
058ac9ba
BB
2160.sp
2161.ne 2
058ac9ba
BB
2162.na
2163\fB\fB-a\fR\fR
2164.ad
2165.RS 14n
b9b24bb4 2166Enables all supported features on all pools.
058ac9ba
BB
2167.RE
2168
2169.sp
2170.ne 2
058ac9ba
BB
2171.na
2172\fB\fB-V\fR \fIversion\fR\fR
2173.ad
2174.RS 14n
b9b24bb4 2175Upgrade to the specified legacy version. If the \fB-V\fR flag is specified, no features will be enabled on the pool. This option can only be used to increase the version number up to the last supported legacy version number.
058ac9ba
BB
2176.RE
2177
2178.RE
2179
2180.SH EXAMPLES
2181.LP
2182\fBExample 1 \fRCreating a RAID-Z Storage Pool
2183.sp
2184.LP
2185The following command creates a pool with a single \fBraidz\fR root \fIvdev\fR that consists of six disks.
2186
2187.sp
2188.in +2
2189.nf
54e5f226 2190# \fBzpool create tank raidz sda sdb sdc sdd sde sdf\fR
058ac9ba
BB
2191.fi
2192.in -2
2193.sp
2194
2195.LP
2196\fBExample 2 \fRCreating a Mirrored Storage Pool
2197.sp
2198.LP
2199The following command creates a pool with two mirrors, where each mirror contains two disks.
2200
2201.sp
2202.in +2
2203.nf
54e5f226 2204# \fBzpool create tank mirror sda sdb mirror sdc sdd\fR
058ac9ba
BB
2205.fi
2206.in -2
2207.sp
2208
2209.LP
54e5f226 2210\fBExample 3 \fRCreating a ZFS Storage Pool by Using Partitions
058ac9ba
BB
2211.sp
2212.LP
54e5f226 2213The following command creates an unmirrored pool using two disk partitions.
058ac9ba
BB
2214
2215.sp
2216.in +2
2217.nf
54e5f226 2218# \fBzpool create tank sda1 sdb2\fR
058ac9ba
BB
2219.fi
2220.in -2
2221.sp
2222
2223.LP
2224\fBExample 4 \fRCreating a ZFS Storage Pool by Using Files
2225.sp
2226.LP
2227The following command creates an unmirrored pool using files. While not recommended, a pool based on files can be useful for experimental purposes.
2228
2229.sp
2230.in +2
2231.nf
2232# \fBzpool create tank /path/to/file/a /path/to/file/b\fR
2233.fi
2234.in -2
2235.sp
2236
2237.LP
2238\fBExample 5 \fRAdding a Mirror to a ZFS Storage Pool
2239.sp
2240.LP
6b92390f 2241The following command adds two mirrored disks to the pool \fItank\fR, assuming the pool is already made up of two-way mirrors. The additional space is immediately available to any datasets within the pool.
058ac9ba
BB
2242
2243.sp
2244.in +2
2245.nf
54e5f226 2246# \fBzpool add tank mirror sda sdb\fR
058ac9ba
BB
2247.fi
2248.in -2
2249.sp
2250
2251.LP
2252\fBExample 6 \fRListing Available ZFS Storage Pools
2253.sp
2254.LP
2255The following command lists all available pools on the system. In this case, the pool \fIzion\fR is faulted due to a missing device.
2256
2257.sp
2258.LP
2259The results from this command are similar to the following:
2260
2261.sp
2262.in +2
2263.nf
2264# \fBzpool list\fR
f3a7f661
GW
2265NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT
2266rpool 19.9G 8.43G 11.4G 33% - 42% 1.00x ONLINE -
2267tank 61.5G 20.0G 41.5G 48% - 32% 1.00x ONLINE -
2268zion - - - - - - - FAULTED -
058ac9ba
BB
2269.fi
2270.in -2
2271.sp
2272
2273.LP
2274\fBExample 7 \fRDestroying a ZFS Storage Pool
2275.sp
2276.LP
6b92390f 2277The following command destroys the pool \fItank\fR and any datasets contained within.
058ac9ba
BB
2278
2279.sp
2280.in +2
2281.nf
2282# \fBzpool destroy -f tank\fR
2283.fi
2284.in -2
2285.sp
2286
2287.LP
2288\fBExample 8 \fRExporting a ZFS Storage Pool
2289.sp
2290.LP
2291The following command exports the devices in pool \fItank\fR so that they can be relocated or later imported.
2292
2293.sp
2294.in +2
2295.nf
2296# \fBzpool export tank\fR
2297.fi
2298.in -2
2299.sp
2300
2301.LP
2302\fBExample 9 \fRImporting a ZFS Storage Pool
2303.sp
2304.LP
6b92390f 2305The following command displays available pools, and then imports the pool \fItank\fR for use on the system.
058ac9ba
BB
2306
2307.sp
2308.LP
2309The results from this command are similar to the following:
2310
2311.sp
2312.in +2
2313.nf
2314# \fBzpool import\fR
2315 pool: tank
2316 id: 15451357997522795478
2317 state: ONLINE
2318action: The pool can be imported using its name or numeric identifier.
2319config:
2320
2321 tank ONLINE
2322 mirror ONLINE
54e5f226
RL
2323 sda ONLINE
2324 sdb ONLINE
058ac9ba
BB
2325
2326# \fBzpool import tank\fR
2327.fi
2328.in -2
2329.sp
2330
2331.LP
2332\fBExample 10 \fRUpgrading All ZFS Storage Pools to the Current Version
2333.sp
2334.LP
2335The following command upgrades all ZFS Storage pools to the current version of the software.
2336
2337.sp
2338.in +2
2339.nf
2340# \fBzpool upgrade -a\fR
251eb26d 2341This system is currently running ZFS pool version 28.
058ac9ba
BB
2342.fi
2343.in -2
2344.sp
2345
2346.LP
2347\fBExample 11 \fRManaging Hot Spares
2348.sp
2349.LP
2350The following command creates a new pool with an available hot spare:
2351
2352.sp
2353.in +2
2354.nf
54e5f226 2355# \fBzpool create tank mirror sda sdb spare sdc\fR
058ac9ba
BB
2356.fi
2357.in -2
2358.sp
2359
2360.sp
2361.LP
2362If one of the disks were to fail, the pool would be reduced to the degraded state. The failed device can be replaced using the following command:
2363
2364.sp
2365.in +2
2366.nf
54e5f226 2367# \fBzpool replace tank sda sdd\fR
058ac9ba
BB
2368.fi
2369.in -2
2370.sp
2371
2372.sp
2373.LP
0d122e21 2374Once the data has been resilvered, the spare is automatically removed and is made available for use should another device fails. The hot spare can be permanently removed from the pool using the following command:
058ac9ba
BB
2375
2376.sp
2377.in +2
2378.nf
54e5f226 2379# \fBzpool remove tank sdc\fR
058ac9ba
BB
2380.fi
2381.in -2
2382.sp
2383
2384.LP
2385\fBExample 12 \fRCreating a ZFS Pool with Mirrored Separate Intent Logs
2386.sp
2387.LP
2388The following command creates a ZFS storage pool consisting of two, two-way mirrors and mirrored log devices:
2389
2390.sp
2391.in +2
2392.nf
54e5f226
RL
2393# \fBzpool create pool mirror sda sdb mirror sdc sdd log mirror \e
2394 sde sdf\fR
058ac9ba
BB
2395.fi
2396.in -2
2397.sp
2398
2399.LP
2400\fBExample 13 \fRAdding Cache Devices to a ZFS Pool
2401.sp
2402.LP
2403The following command adds two disks for use as cache devices to a ZFS storage pool:
2404
2405.sp
2406.in +2
2407.nf
54e5f226 2408# \fBzpool add pool cache sdc sdd\fR
058ac9ba
BB
2409.fi
2410.in -2
2411.sp
2412
2413.sp
2414.LP
6b4e21c6 2415Once added, the cache devices gradually fill with content from main memory. Depending on the size of your cache devices, it could take over an hour for them to fill. Capacity and reads can be monitored using the \fBiostat\fR option as follows:
058ac9ba
BB
2416
2417.sp
2418.in +2
2419.nf
2420# \fBzpool iostat -v pool 5\fR
2421.fi
2422.in -2
2423.sp
2424
2425.LP
2426\fBExample 14 \fRRemoving a Mirrored Log Device
2427.sp
2428.LP
2429The following command removes the mirrored log device \fBmirror-2\fR.
2430
2431.sp
2432.LP
2433Given this configuration:
2434
2435.sp
2436.in +2
2437.nf
2438 pool: tank
2439 state: ONLINE
2440 scrub: none requested
2441config:
2442
2443 NAME STATE READ WRITE CKSUM
2444 tank ONLINE 0 0 0
2445 mirror-0 ONLINE 0 0 0
54e5f226
RL
2446 sda ONLINE 0 0 0
2447 sdb ONLINE 0 0 0
058ac9ba 2448 mirror-1 ONLINE 0 0 0
54e5f226
RL
2449 sdc ONLINE 0 0 0
2450 sdd ONLINE 0 0 0
058ac9ba
BB
2451 logs
2452 mirror-2 ONLINE 0 0 0
54e5f226
RL
2453 sde ONLINE 0 0 0
2454 sdf ONLINE 0 0 0
058ac9ba
BB
2455.fi
2456.in -2
2457.sp
2458
2459.sp
2460.LP
2461The command to remove the mirrored log \fBmirror-2\fR is:
2462
2463.sp
2464.in +2
2465.nf
2466# \fBzpool remove tank mirror-2\fR
2467.fi
2468.in -2
2469.sp
2470
1bd201e7
CS
2471.LP
2472\fBExample 15 \fRDisplaying expanded space on a device
2473.sp
2474.LP
f3a7f661 2475The following command displays the detailed information for the \fIdata\fR
1bd201e7 2476pool. This pool is comprised of a single \fIraidz\fR vdev where one of its
6b4e21c6 2477devices increased its capacity by 10GB. In this example, the pool will not
1bd201e7
CS
2478be able to utilized this extra capacity until all the devices under the
2479\fIraidz\fR vdev have been expanded.
2480
2481.sp
2482.in +2
2483.nf
2484# \fBzpool list -v data\fR
f3a7f661
GW
2485NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT
2486data 23.9G 14.6G 9.30G 48% - 61% 1.00x ONLINE -
2487 raidz1 23.9G 14.6G 9.30G 48% -
2488 c1t1d0 - - - - -
2489 c1t2d0 - - - - 10G
2490 c1t3d0 - - - - -
1bd201e7
CS
2491.fi
2492.in -2
2493
058ac9ba
BB
2494.SH EXIT STATUS
2495.sp
2496.LP
2497The following exit values are returned:
2498.sp
2499.ne 2
058ac9ba
BB
2500.na
2501\fB\fB0\fR\fR
2502.ad
2503.RS 5n
6b4e21c6 2504Successful completion.
058ac9ba
BB
2505.RE
2506
2507.sp
2508.ne 2
058ac9ba
BB
2509.na
2510\fB\fB1\fR\fR
2511.ad
2512.RS 5n
058ac9ba
BB
2513An error occurred.
2514.RE
2515
2516.sp
2517.ne 2
058ac9ba
BB
2518.na
2519\fB\fB2\fR\fR
2520.ad
2521.RS 5n
058ac9ba
BB
2522Invalid command line options were specified.
2523.RE
2524
71bd0645
TF
2525.SH "ENVIRONMENT VARIABLES"
2526.TP
2527.B "ZFS_ABORT
2528Cause \fBzpool\fR to dump core on exit for the purposes of running \fB::findleaks\fR.
2529.TP
2530.B "ZPOOL_IMPORT_PATH"
2531The search path for devices or files to use with the pool. This is a colon-separated list of directories in which \fBzpool\fR looks for device nodes and files.
2532Similar to the \fB-d\fR option in \fIzpool import\fR.
d2f3e292
RY
2533.TP
2534.B "ZPOOL_VDEV_NAME_GUID"
2535Cause \fBzpool\fR subcommands to output vdev guids by default. This behavior
2536is identical to the \fBzpool status -g\fR command line option.
2537.TP
2538.B "ZPOOL_VDEV_NAME_FOLLOW_LINKS"
2539Cause \fBzpool\fR subcommands to follow links for vdev names by default. This behavior is identical to the \fBzpool status -L\fR command line option.
2540.TP
2541.B "ZPOOL_VDEV_NAME_PATH"
2542Cause \fBzpool\fR subcommands to output full vdev path names by default. This
2543behavior is identical to the \fBzpool status -p\fR command line option.
39fc0cb5
DB
2544.TP
2545.B "ZFS_VDEV_DEVID_OPT_OUT"
2546Older ZFS on Linux implementations had issues when attempting to display pool
2547config VDEV names if a "devid" NVP value is present in the pool's config.
2548
2549For example, a pool that originated on illumos platform would have a devid
2550value in the config and \fBzpool status\fR would fail when listing the config.
2551This would also be true for future Linux based pools.
2552
2553A pool can be stripped of any "devid" values on import or prevented from adding
2554them on \fBzpool create\fR or \fBzpool add\fR by setting ZFS_VDEV_DEVID_OPT_OUT.
71bd0645 2555
058ac9ba
BB
2556.SH SEE ALSO
2557.sp
2558.LP
83426735 2559\fBzfs\fR(8), \fBzpool-features\fR(5), \fBzfs-events\fR(5), \fBzfs-module-parameters\fR(5)