Skip to content

Commit

Permalink
zpool-remove.8: describe top-level vdev sector size limitation
Browse files Browse the repository at this point in the history
Document that top-level vdevs cannot be removed unless all top-level
vdevs have the same sector size.

Signed-off-by: Sam Hathaway <sam@sam-hathaway.com>
Closes: #11339
  • Loading branch information
smammy committed Aug 12, 2021
1 parent 6bc61d2 commit 55560c1
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions man/man8/zpool-remove.8
Original file line number Diff line number Diff line change
Expand Up @@ -52,10 +52,10 @@
Removes the specified device from the pool.
This command supports removing hot spare, cache, log, and both mirrored and
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,
cache, and log devices can be removed.
Note that keys for all encrypted datasets must be loaded for top-level vdevs
to be removed.
.Pp
Top-level vdevs can only be removed if the primary pool storage does not contain
a top-level raidz vdev, all top-level vdevs have the same sector size, and the
keys for all encrypted datasets are loaded.
.Pp
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
Expand Down

0 comments on commit 55560c1

Please sign in to comment.