Comment by ryao

Comment by ryao 5 days ago

That was added a while ago:

https://openzfs.github.io/openzfs-docs/man/master/8/zpool-re...

It works by making a readonly copy of the vdev being removed inside the remaining space. The existing vdev is then removed. Data can still be accessed from the copy, but new writes will go to an actual vdev while data no longer needed on the copy is gradually reclaimed as free space as the old data is no longer needed.

lutorm 5 days ago

Although "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."

Reply View 3 replies

ryao 5 days ago

I forgot we still did not have that last bit implemented. However, it is less important now that we have expansion.

Reply View | 1 reply
- justinclift 4 days ago
  
  > However, it is less important now that we have expansion.
  Not really sure if that's true. They seem like two different/distinct use cases, though there's probably some small overlap.
  
  Reply View | 0 replies
cm2187 5 days ago

And in my case all the vdevs are raidz

Reply View | 0 replies