2019-11-13 20:21:07 +03:00
|
|
|
.\"
|
|
|
|
|
.\" CDDL HEADER START
|
|
|
|
|
.\"
|
|
|
|
|
.\" The contents of this file are subject to the terms of the
|
|
|
|
|
.\" Common Development and Distribution License (the "License").
|
|
|
|
|
.\" You may not use this file except in compliance with the License.
|
|
|
|
|
.\"
|
|
|
|
|
.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
|
2022-07-12 00:16:13 +03:00
|
|
|
.\" or https://opensource.org/licenses/CDDL-1.0.
|
2019-11-13 20:21:07 +03:00
|
|
|
.\" See the License for the specific language governing permissions
|
|
|
|
|
.\" and limitations under the License.
|
|
|
|
|
.\"
|
|
|
|
|
.\" When distributing Covered Code, include this CDDL HEADER in each
|
|
|
|
|
.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
|
|
|
|
|
.\" If applicable, add the following below this CDDL HEADER, with the
|
|
|
|
|
.\" fields enclosed by brackets "[]" replaced with your own identifying
|
|
|
|
|
.\" information: Portions Copyright [yyyy] [name of copyright owner]
|
|
|
|
|
.\"
|
|
|
|
|
.\" CDDL HEADER END
|
|
|
|
|
.\"
|
|
|
|
|
.\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
|
|
|
|
|
.\" Copyright (c) 2012, 2018 by Delphix. All rights reserved.
|
|
|
|
|
.\" Copyright (c) 2012 Cyril Plisko. All Rights Reserved.
|
|
|
|
|
.\" Copyright (c) 2017 Datto Inc.
|
|
|
|
|
.\" Copyright (c) 2018 George Melikov. All Rights Reserved.
|
|
|
|
|
.\" Copyright 2017 Nexenta Systems, Inc.
|
|
|
|
|
.\" Copyright (c) 2017 Open-E, Inc. All Rights Reserved.
|
|
|
|
|
.\"
|
2024-07-26 19:16:18 +03:00
|
|
|
.Dd February 14, 2024
|
2019-11-13 20:21:07 +03:00
|
|
|
.Dt ZPOOL-STATUS 8
|
2020-08-21 21:55:47 +03:00
|
|
|
.Os
|
2021-05-27 03:46:40 +03:00
|
|
|
.
|
2019-11-13 20:21:07 +03:00
|
|
|
.Sh NAME
|
2020-10-22 21:28:10 +03:00
|
|
|
.Nm zpool-status
|
2021-05-27 03:46:40 +03:00
|
|
|
.Nd show detailed health status for ZFS storage pools
|
2019-11-13 20:21:07 +03:00
|
|
|
.Sh SYNOPSIS
|
2020-10-22 21:28:10 +03:00
|
|
|
.Nm zpool
|
2019-11-13 20:21:07 +03:00
|
|
|
.Cm status
|
Adding Direct IO Support
Adding O_DIRECT support to ZFS to bypass the ARC for writes/reads.
O_DIRECT support in ZFS will always ensure there is coherency between
buffered and O_DIRECT IO requests. This ensures that all IO requests,
whether buffered or direct, will see the same file contents at all
times. Just as in other FS's , O_DIRECT does not imply O_SYNC. While
data is written directly to VDEV disks, metadata will not be synced
until the associated TXG is synced.
For both O_DIRECT read and write request the offset and request sizes,
at a minimum, must be PAGE_SIZE aligned. In the event they are not,
then EINVAL is returned unless the direct property is set to always (see
below).
For O_DIRECT writes:
The request also must be block aligned (recordsize) or the write
request will take the normal (buffered) write path. In the event that
request is block aligned and a cached copy of the buffer in the ARC,
then it will be discarded from the ARC forcing all further reads to
retrieve the data from disk.
For O_DIRECT reads:
The only alignment restrictions are PAGE_SIZE alignment. In the event
that the requested data is in buffered (in the ARC) it will just be
copied from the ARC into the user buffer.
For both O_DIRECT writes and reads the O_DIRECT flag will be ignored in
the event that file contents are mmap'ed. In this case, all requests
that are at least PAGE_SIZE aligned will just fall back to the buffered
paths. If the request however is not PAGE_SIZE aligned, EINVAL will
be returned as always regardless if the file's contents are mmap'ed.
Since O_DIRECT writes go through the normal ZIO pipeline, the
following operations are supported just as with normal buffered writes:
Checksum
Compression
Encryption
Erasure Coding
There is one caveat for the data integrity of O_DIRECT writes that is
distinct for each of the OS's supported by ZFS.
FreeBSD - FreeBSD is able to place user pages under write protection so
any data in the user buffers and written directly down to the
VDEV disks is guaranteed to not change. There is no concern
with data integrity and O_DIRECT writes.
Linux - Linux is not able to place anonymous user pages under write
protection. Because of this, if the user decides to manipulate
the page contents while the write operation is occurring, data
integrity can not be guaranteed. However, there is a module
parameter `zfs_vdev_direct_write_verify` that controls the
if a O_DIRECT writes that can occur to a top-level VDEV before
a checksum verify is run before the contents of the I/O buffer
are committed to disk. In the event of a checksum verification
failure the write will return EIO. The number of O_DIRECT write
checksum verification errors can be observed by doing
`zpool status -d`, which will list all verification errors that
have occurred on a top-level VDEV. Along with `zpool status`, a
ZED event will be issues as `dio_verify` when a checksum
verification error occurs.
ZVOLs and dedup is not currently supported with Direct I/O.
A new dataset property `direct` has been added with the following 3
allowable values:
disabled - Accepts O_DIRECT flag, but silently ignores it and treats
the request as a buffered IO request.
standard - Follows the alignment restrictions outlined above for
write/read IO requests when the O_DIRECT flag is used.
always - Treats every write/read IO request as though it passed
O_DIRECT and will do O_DIRECT if the alignment restrictions
are met otherwise will redirect through the ARC. This
property will not allow a request to fail.
There is also a module parameter zfs_dio_enabled that can be used to
force all reads and writes through the ARC. By setting this module
parameter to 0, it mimics as if the direct dataset property is set to
disabled.
Reviewed-by: Brian Behlendorf <behlendorf@llnl.gov>
Reviewed-by: Alexander Motin <mav@FreeBSD.org>
Reviewed-by: Tony Hutter <hutter2@llnl.gov>
Signed-off-by: Brian Atkinson <batkinson@lanl.gov>
Co-authored-by: Mark Maybee <mark.maybee@delphix.com>
Co-authored-by: Matt Macy <mmacy@FreeBSD.org>
Co-authored-by: Brian Behlendorf <behlendorf@llnl.gov>
Closes #10018
2024-09-14 23:47:59 +03:00
|
|
|
.Op Fl dDegiLpPstvx
|
2019-11-13 20:21:07 +03:00
|
|
|
.Op Fl T Sy u Ns | Ns Sy d
|
2021-05-27 03:46:40 +03:00
|
|
|
.Op Fl c Op Ar SCRIPT1 Ns Oo , Ns Ar SCRIPT2 Oc Ns …
|
|
|
|
|
.Oo Ar pool Oc Ns …
|
2019-11-13 20:21:07 +03:00
|
|
|
.Op Ar interval Op Ar count
|
2024-05-09 14:54:47 +03:00
|
|
|
.Op Fl j Op Ar --json-int, --json-flat-vdevs, --json-pool-key-guid
|
2021-05-27 03:46:40 +03:00
|
|
|
.
|
2019-11-13 20:21:07 +03:00
|
|
|
.Sh DESCRIPTION
|
|
|
|
|
Displays the detailed health status for the given pools.
|
|
|
|
|
If no
|
|
|
|
|
.Ar pool
|
|
|
|
|
is specified, then the status of each pool in the system is displayed.
|
|
|
|
|
For more information on pool and device health, see the
|
2021-05-27 03:46:40 +03:00
|
|
|
.Sx Device Failure and Recovery
|
2019-11-13 20:21:07 +03:00
|
|
|
section of
|
2021-06-04 23:29:26 +03:00
|
|
|
.Xr zpoolconcepts 7 .
|
2019-11-13 20:21:07 +03:00
|
|
|
.Pp
|
|
|
|
|
If 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.
|
|
|
|
|
.Bl -tag -width Ds
|
2023-12-21 21:53:16 +03:00
|
|
|
.It Fl -power
|
|
|
|
|
Display vdev enclosure slot power status (on or off).
|
2021-05-27 03:46:40 +03:00
|
|
|
.It Fl c Op Ar SCRIPT1 Ns Oo , Ns Ar SCRIPT2 Oc Ns …
|
2019-11-13 20:21:07 +03:00
|
|
|
Run a script (or scripts) on each vdev and include the output as a new column
|
|
|
|
|
in the
|
|
|
|
|
.Nm zpool Cm status
|
2021-05-27 03:46:40 +03:00
|
|
|
output.
|
|
|
|
|
See the
|
2019-11-13 20:21:07 +03:00
|
|
|
.Fl c
|
|
|
|
|
option of
|
|
|
|
|
.Nm zpool Cm iostat
|
|
|
|
|
for complete details.
|
2024-05-09 14:54:47 +03:00
|
|
|
.It Fl j Op Ar --json-int, --json-flat-vdevs, --json-pool-key-guid
|
|
|
|
|
Display the status for ZFS pools in JSON format.
|
|
|
|
|
Specify
|
|
|
|
|
.Sy --json-int
|
|
|
|
|
to display numbers in integer format instead of strings.
|
|
|
|
|
Specify
|
|
|
|
|
.Sy --json-flat-vdevs
|
|
|
|
|
to display vdevs in flat hierarchy instead of nested vdev objects.
|
|
|
|
|
Specify
|
|
|
|
|
.Sy --json-pool-key-guid
|
|
|
|
|
to set pool GUID as key for pool objects instead of pool names.
|
Adding Direct IO Support
Adding O_DIRECT support to ZFS to bypass the ARC for writes/reads.
O_DIRECT support in ZFS will always ensure there is coherency between
buffered and O_DIRECT IO requests. This ensures that all IO requests,
whether buffered or direct, will see the same file contents at all
times. Just as in other FS's , O_DIRECT does not imply O_SYNC. While
data is written directly to VDEV disks, metadata will not be synced
until the associated TXG is synced.
For both O_DIRECT read and write request the offset and request sizes,
at a minimum, must be PAGE_SIZE aligned. In the event they are not,
then EINVAL is returned unless the direct property is set to always (see
below).
For O_DIRECT writes:
The request also must be block aligned (recordsize) or the write
request will take the normal (buffered) write path. In the event that
request is block aligned and a cached copy of the buffer in the ARC,
then it will be discarded from the ARC forcing all further reads to
retrieve the data from disk.
For O_DIRECT reads:
The only alignment restrictions are PAGE_SIZE alignment. In the event
that the requested data is in buffered (in the ARC) it will just be
copied from the ARC into the user buffer.
For both O_DIRECT writes and reads the O_DIRECT flag will be ignored in
the event that file contents are mmap'ed. In this case, all requests
that are at least PAGE_SIZE aligned will just fall back to the buffered
paths. If the request however is not PAGE_SIZE aligned, EINVAL will
be returned as always regardless if the file's contents are mmap'ed.
Since O_DIRECT writes go through the normal ZIO pipeline, the
following operations are supported just as with normal buffered writes:
Checksum
Compression
Encryption
Erasure Coding
There is one caveat for the data integrity of O_DIRECT writes that is
distinct for each of the OS's supported by ZFS.
FreeBSD - FreeBSD is able to place user pages under write protection so
any data in the user buffers and written directly down to the
VDEV disks is guaranteed to not change. There is no concern
with data integrity and O_DIRECT writes.
Linux - Linux is not able to place anonymous user pages under write
protection. Because of this, if the user decides to manipulate
the page contents while the write operation is occurring, data
integrity can not be guaranteed. However, there is a module
parameter `zfs_vdev_direct_write_verify` that controls the
if a O_DIRECT writes that can occur to a top-level VDEV before
a checksum verify is run before the contents of the I/O buffer
are committed to disk. In the event of a checksum verification
failure the write will return EIO. The number of O_DIRECT write
checksum verification errors can be observed by doing
`zpool status -d`, which will list all verification errors that
have occurred on a top-level VDEV. Along with `zpool status`, a
ZED event will be issues as `dio_verify` when a checksum
verification error occurs.
ZVOLs and dedup is not currently supported with Direct I/O.
A new dataset property `direct` has been added with the following 3
allowable values:
disabled - Accepts O_DIRECT flag, but silently ignores it and treats
the request as a buffered IO request.
standard - Follows the alignment restrictions outlined above for
write/read IO requests when the O_DIRECT flag is used.
always - Treats every write/read IO request as though it passed
O_DIRECT and will do O_DIRECT if the alignment restrictions
are met otherwise will redirect through the ARC. This
property will not allow a request to fail.
There is also a module parameter zfs_dio_enabled that can be used to
force all reads and writes through the ARC. By setting this module
parameter to 0, it mimics as if the direct dataset property is set to
disabled.
Reviewed-by: Brian Behlendorf <behlendorf@llnl.gov>
Reviewed-by: Alexander Motin <mav@FreeBSD.org>
Reviewed-by: Tony Hutter <hutter2@llnl.gov>
Signed-off-by: Brian Atkinson <batkinson@lanl.gov>
Co-authored-by: Mark Maybee <mark.maybee@delphix.com>
Co-authored-by: Matt Macy <mmacy@FreeBSD.org>
Co-authored-by: Brian Behlendorf <behlendorf@llnl.gov>
Closes #10018
2024-09-14 23:47:59 +03:00
|
|
|
.It Fl d
|
|
|
|
|
Display the number of Direct I/O write checksum verify errors that have occured
|
|
|
|
|
on a top-level VDEV.
|
|
|
|
|
See
|
|
|
|
|
.Sx zfs_vdev_direct_write_verify
|
|
|
|
|
in
|
|
|
|
|
.Xr zfs 4
|
|
|
|
|
for details about the conditions that can cause Direct I/O write checksum
|
|
|
|
|
verify failures to occur.
|
2024-03-21 19:00:29 +03:00
|
|
|
.It Fl D
|
|
|
|
|
Display a histogram of deduplication statistics, showing the allocated
|
|
|
|
|
.Pq physically present on disk
|
|
|
|
|
and referenced
|
|
|
|
|
.Pq logically referenced in the pool
|
|
|
|
|
block counts and sizes by reference count.
|
2024-07-26 19:16:18 +03:00
|
|
|
If repeated, (-DD), also shows statistics on how much of the DDT is resident
|
|
|
|
|
in the ARC.
|
2024-02-07 20:12:12 +03:00
|
|
|
.It Fl e
|
|
|
|
|
Only show unhealthy vdevs (not-ONLINE or with errors).
|
2019-11-13 20:21:07 +03:00
|
|
|
.It Fl g
|
2021-05-27 03:46:40 +03:00
|
|
|
Display vdev GUIDs instead of the normal device names
|
|
|
|
|
These GUIDs can be used in place of device names for the zpool
|
2019-11-13 20:21:07 +03:00
|
|
|
detach/offline/remove/replace commands.
|
2024-03-21 19:00:29 +03:00
|
|
|
.It Fl i
|
|
|
|
|
Display vdev initialization status.
|
2019-11-13 20:21:07 +03:00
|
|
|
.It Fl L
|
2021-05-27 03:46:40 +03:00
|
|
|
Display real paths for vdevs resolving all symbolic links.
|
|
|
|
|
This can be used to look up the current block device name regardless of the
|
2019-11-13 20:21:07 +03:00
|
|
|
.Pa /dev/disk/
|
|
|
|
|
path used to open it.
|
|
|
|
|
.It Fl p
|
|
|
|
|
Display numbers in parsable (exact) values.
|
|
|
|
|
.It Fl P
|
|
|
|
|
Display full paths for vdevs instead of only the last component of
|
2021-05-27 03:46:40 +03:00
|
|
|
the path.
|
|
|
|
|
This can be used in conjunction with the
|
2019-11-13 20:21:07 +03:00
|
|
|
.Fl L
|
|
|
|
|
flag.
|
|
|
|
|
.It Fl s
|
2022-02-17 23:26:43 +03:00
|
|
|
Display the number of leaf vdev slow I/O operations.
|
|
|
|
|
This is the number of I/O operations that didn't complete in
|
2021-05-27 03:46:40 +03:00
|
|
|
.Sy zio_slow_io_ms
|
2022-02-17 23:26:43 +03:00
|
|
|
milliseconds
|
|
|
|
|
.Pq Sy 30000 No by default .
|
2022-11-12 15:23:30 +03:00
|
|
|
This does not necessarily mean the I/O operations failed to complete, just took
|
|
|
|
|
an
|
2021-05-27 03:46:40 +03:00
|
|
|
unreasonably long amount of time.
|
|
|
|
|
This may indicate a problem with the underlying storage.
|
2019-11-13 20:21:07 +03:00
|
|
|
.It Fl t
|
|
|
|
|
Display vdev TRIM status.
|
|
|
|
|
.It Fl T Sy u Ns | Ns Sy d
|
|
|
|
|
Display a time stamp.
|
|
|
|
|
Specify
|
|
|
|
|
.Sy u
|
|
|
|
|
for a printed representation of the internal representation of time.
|
|
|
|
|
See
|
2024-01-29 20:44:08 +03:00
|
|
|
.Xr time 1 .
|
2019-11-13 20:21:07 +03:00
|
|
|
Specify
|
|
|
|
|
.Sy d
|
|
|
|
|
for standard date format.
|
|
|
|
|
See
|
|
|
|
|
.Xr date 1 .
|
|
|
|
|
.It Fl v
|
|
|
|
|
Displays verbose data error information, printing out a complete list of all
|
|
|
|
|
data errors since the last complete pool scrub.
|
2023-05-09 18:53:27 +03:00
|
|
|
If the head_errlog feature is enabled and files containing errors have been
|
|
|
|
|
removed then the respective filenames will not be reported in subsequent runs
|
|
|
|
|
of this command.
|
2019-11-13 20:21:07 +03:00
|
|
|
.It Fl x
|
|
|
|
|
Only 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.
|
|
|
|
|
.El
|
2021-05-27 03:46:40 +03:00
|
|
|
.
|
2022-03-16 20:04:41 +03:00
|
|
|
.Sh EXAMPLES
|
|
|
|
|
.\" These are, respectively, examples 16 from zpool.8
|
|
|
|
|
.\" Make sure to update them bidirectionally
|
|
|
|
|
.Ss Example 1 : No Adding output columns
|
|
|
|
|
Additional columns can be added to the
|
|
|
|
|
.Nm zpool Cm status No and Nm zpool Cm iostat No output with Fl c .
|
|
|
|
|
.Bd -literal -compact -offset Ds
|
|
|
|
|
.No # Nm zpool Cm status Fl c Pa vendor , Ns Pa model , Ns Pa size
|
|
|
|
|
NAME STATE READ WRITE CKSUM vendor model size
|
|
|
|
|
tank ONLINE 0 0 0
|
|
|
|
|
mirror-0 ONLINE 0 0 0
|
|
|
|
|
U1 ONLINE 0 0 0 SEAGATE ST8000NM0075 7.3T
|
|
|
|
|
U10 ONLINE 0 0 0 SEAGATE ST8000NM0075 7.3T
|
|
|
|
|
U11 ONLINE 0 0 0 SEAGATE ST8000NM0075 7.3T
|
|
|
|
|
U12 ONLINE 0 0 0 SEAGATE ST8000NM0075 7.3T
|
|
|
|
|
U13 ONLINE 0 0 0 SEAGATE ST8000NM0075 7.3T
|
|
|
|
|
U14 ONLINE 0 0 0 SEAGATE ST8000NM0075 7.3T
|
|
|
|
|
|
|
|
|
|
.No # Nm zpool Cm iostat Fl vc Pa size
|
|
|
|
|
capacity operations bandwidth
|
|
|
|
|
pool alloc free read write read write size
|
|
|
|
|
---------- ----- ----- ----- ----- ----- ----- ----
|
|
|
|
|
rpool 14.6G 54.9G 4 55 250K 2.69M
|
|
|
|
|
sda1 14.6G 54.9G 4 55 250K 2.69M 70G
|
|
|
|
|
---------- ----- ----- ----- ----- ----- ----- ----
|
|
|
|
|
.Ed
|
|
|
|
|
.
|
2024-05-09 14:54:47 +03:00
|
|
|
.Ss Example 2 : No Display the status output in JSON format
|
|
|
|
|
.Nm zpool Cm status No can output in JSON format if
|
|
|
|
|
.Fl j
|
|
|
|
|
is specified.
|
|
|
|
|
.Fl c
|
|
|
|
|
can be used to run a script on each VDEV.
|
|
|
|
|
.Bd -literal -compact -offset Ds
|
|
|
|
|
.No # Nm zpool Cm status Fl j Fl c Pa vendor , Ns Pa model , Ns Pa size | Nm jq
|
|
|
|
|
{
|
|
|
|
|
"output_version": {
|
|
|
|
|
"command": "zpool status",
|
|
|
|
|
"vers_major": 0,
|
|
|
|
|
"vers_minor": 1
|
|
|
|
|
},
|
|
|
|
|
"pools": {
|
|
|
|
|
"tank": {
|
|
|
|
|
"name": "tank",
|
|
|
|
|
"state": "ONLINE",
|
|
|
|
|
"guid": "3920273586464696295",
|
|
|
|
|
"txg": "16597",
|
|
|
|
|
"spa_version": "5000",
|
|
|
|
|
"zpl_version": "5",
|
|
|
|
|
"status": "OK",
|
|
|
|
|
"vdevs": {
|
|
|
|
|
"tank": {
|
|
|
|
|
"name": "tank",
|
|
|
|
|
"alloc_space": "62.6G",
|
|
|
|
|
"total_space": "15.0T",
|
|
|
|
|
"def_space": "11.3T",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vdevs": {
|
|
|
|
|
"raidz1-0": {
|
|
|
|
|
"name": "raidz1-0",
|
|
|
|
|
"vdev_type": "raidz",
|
|
|
|
|
"guid": "763132626387621737",
|
|
|
|
|
"state": "HEALTHY",
|
|
|
|
|
"alloc_space": "62.5G",
|
|
|
|
|
"total_space": "10.9T",
|
|
|
|
|
"def_space": "7.26T",
|
|
|
|
|
"rep_dev_size": "10.9T",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vdevs": {
|
|
|
|
|
"ca1eb824-c371-491d-ac13-37637e35c683": {
|
|
|
|
|
"name": "ca1eb824-c371-491d-ac13-37637e35c683",
|
|
|
|
|
"vdev_type": "disk",
|
|
|
|
|
"guid": "12841765308123764671",
|
|
|
|
|
"path": "/dev/disk/by-partuuid/ca1eb824-c371-491d-ac13-37637e35c683",
|
|
|
|
|
"state": "HEALTHY",
|
|
|
|
|
"rep_dev_size": "3.64T",
|
|
|
|
|
"phys_space": "3.64T",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vendor": "ATA",
|
|
|
|
|
"model": "WDC WD40EFZX-68AWUN0",
|
|
|
|
|
"size": "3.6T"
|
|
|
|
|
},
|
|
|
|
|
"97cd98fb-8fb8-4ac4-bc84-bd8950a7ace7": {
|
|
|
|
|
"name": "97cd98fb-8fb8-4ac4-bc84-bd8950a7ace7",
|
|
|
|
|
"vdev_type": "disk",
|
|
|
|
|
"guid": "1527839927278881561",
|
|
|
|
|
"path": "/dev/disk/by-partuuid/97cd98fb-8fb8-4ac4-bc84-bd8950a7ace7",
|
|
|
|
|
"state": "HEALTHY",
|
|
|
|
|
"rep_dev_size": "3.64T",
|
|
|
|
|
"phys_space": "3.64T",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vendor": "ATA",
|
|
|
|
|
"model": "WDC WD40EFZX-68AWUN0",
|
|
|
|
|
"size": "3.6T"
|
|
|
|
|
},
|
|
|
|
|
"e9ddba5f-f948-4734-a472-cb8aa5f0ff65": {
|
|
|
|
|
"name": "e9ddba5f-f948-4734-a472-cb8aa5f0ff65",
|
|
|
|
|
"vdev_type": "disk",
|
|
|
|
|
"guid": "6982750226085199860",
|
|
|
|
|
"path": "/dev/disk/by-partuuid/e9ddba5f-f948-4734-a472-cb8aa5f0ff65",
|
|
|
|
|
"state": "HEALTHY",
|
|
|
|
|
"rep_dev_size": "3.64T",
|
|
|
|
|
"phys_space": "3.64T",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vendor": "ATA",
|
|
|
|
|
"model": "WDC WD40EFZX-68AWUN0",
|
|
|
|
|
"size": "3.6T"
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"dedup": {
|
|
|
|
|
"mirror-2": {
|
|
|
|
|
"name": "mirror-2",
|
|
|
|
|
"vdev_type": "mirror",
|
|
|
|
|
"guid": "2227766268377771003",
|
|
|
|
|
"state": "HEALTHY",
|
|
|
|
|
"alloc_space": "89.1M",
|
|
|
|
|
"total_space": "3.62T",
|
|
|
|
|
"def_space": "3.62T",
|
|
|
|
|
"rep_dev_size": "3.62T",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vdevs": {
|
|
|
|
|
"db017360-d8e9-4163-961b-144ca75293a3": {
|
|
|
|
|
"name": "db017360-d8e9-4163-961b-144ca75293a3",
|
|
|
|
|
"vdev_type": "disk",
|
|
|
|
|
"guid": "17880913061695450307",
|
|
|
|
|
"path": "/dev/disk/by-partuuid/db017360-d8e9-4163-961b-144ca75293a3",
|
|
|
|
|
"state": "HEALTHY",
|
|
|
|
|
"rep_dev_size": "3.63T",
|
|
|
|
|
"phys_space": "3.64T",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vendor": "ATA",
|
|
|
|
|
"model": "WDC WD40EFZX-68AWUN0",
|
|
|
|
|
"size": "3.6T"
|
|
|
|
|
},
|
|
|
|
|
"952c3baf-b08a-4a8c-b7fa-33a07af5fe6f": {
|
|
|
|
|
"name": "952c3baf-b08a-4a8c-b7fa-33a07af5fe6f",
|
|
|
|
|
"vdev_type": "disk",
|
|
|
|
|
"guid": "10276374011610020557",
|
|
|
|
|
"path": "/dev/disk/by-partuuid/952c3baf-b08a-4a8c-b7fa-33a07af5fe6f",
|
|
|
|
|
"state": "HEALTHY",
|
|
|
|
|
"rep_dev_size": "3.63T",
|
|
|
|
|
"phys_space": "3.64T",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vendor": "ATA",
|
|
|
|
|
"model": "WDC WD40EFZX-68AWUN0",
|
|
|
|
|
"size": "3.6T"
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"special": {
|
|
|
|
|
"25d418f8-92bd-4327-b59f-7ef5d5f50d81": {
|
|
|
|
|
"name": "25d418f8-92bd-4327-b59f-7ef5d5f50d81",
|
|
|
|
|
"vdev_type": "disk",
|
|
|
|
|
"guid": "3935742873387713123",
|
|
|
|
|
"path": "/dev/disk/by-partuuid/25d418f8-92bd-4327-b59f-7ef5d5f50d81",
|
|
|
|
|
"state": "HEALTHY",
|
|
|
|
|
"alloc_space": "37.4M",
|
|
|
|
|
"total_space": "444G",
|
|
|
|
|
"def_space": "444G",
|
|
|
|
|
"rep_dev_size": "444G",
|
|
|
|
|
"phys_space": "447G",
|
|
|
|
|
"read_errors": "0",
|
|
|
|
|
"write_errors": "0",
|
|
|
|
|
"checksum_errors": "0",
|
|
|
|
|
"vendor": "ATA",
|
|
|
|
|
"model": "Micron_5300_MTFDDAK480TDS",
|
|
|
|
|
"size": "447.1G"
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"error_count": "0"
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
.Ed
|
|
|
|
|
.
|
2019-11-13 20:21:07 +03:00
|
|
|
.Sh SEE ALSO
|
|
|
|
|
.Xr zpool-events 8 ,
|
|
|
|
|
.Xr zpool-history 8 ,
|
|
|
|
|
.Xr zpool-iostat 8 ,
|
|
|
|
|
.Xr zpool-list 8 ,
|
|
|
|
|
.Xr zpool-resilver 8 ,
|
|
|
|
|
.Xr zpool-scrub 8 ,
|
|
|
|
|
.Xr zpool-wait 8
|