3 ms·
That was added a while ago: https://openzfs.github.io/openzfs-docs/man/master/8/zpool-remove.8.html https://openzfs.github.io/openzfs-docs/man/master/8/zpool-r
by ryao 2y ago
That was added a while ago:
https://openzfs.github.io/openzfs-docs/man/master/8/zpool-remove.8.html 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 2y agoAlthough "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."
- ryao 2y agoI forgot we still did not have that last bit implemented. However, it is less important now that we have expansion.
- justinclift 2y 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.
- cm2187 2y agoAnd in my case all the vdevs are raidz