Archive-Team
/
zfs
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 103 Wiki Activity

zpool-remove.8: describe top-level vdev sector size limitation 

Document that top-level vdevs cannot be removed unless all top-level
vdevs have the same sector size.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: George Melikov <mail@gmelikov.ru>
Signed-off-by: Sam Hathaway <sam@sam-hathaway.com>
Closes #11339
Closes #12472
This commit is contained in:
Sam Hathaway 2021-08-23 17:59:18 -04:00 committed by Tony Hutter
parent 2016d7fb9c
commit e78d06f89b
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
man/man8/zpool-remove.8
View File

@ -52,10 +52,10 @@
Removes the specified device from the pool. Removes the specified device from the pool.
This command supports removing hot spare, cache, log, and both mirrored and This command supports removing hot spare, cache, log, and both mirrored and
non-redundant primary top-level vdevs, including dedup and special vdevs. non-redundant primary top-level vdevs, including dedup and special vdevs.
When the primary pool storage includes a top-level raidz vdev only hot spare, .Pp
cache, and log devices can be removed. Top-level vdevs can only be removed if the primary pool storage does not contain
Note that keys for all encrypted datasets must be loaded for top-level vdevs a top-level raidz vdev, all top-level vdevs have the same sector size, and the
to be removed. keys for all encrypted datasets are loaded.
.Pp .Pp
Removing a top-level vdev reduces the total amount of space in the storage pool. Removing a top-level vdev reduces the total amount of space in the storage pool.
The specified device will be evacuated by copying all allocated space from it to The specified device will be evacuated by copying all allocated space from it to