Re:ZFS 2.3.0 released with ZFS raidz expansion
by lutorm on Tuesday January 14, 2025 @04:00AM
(#42695187)
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."
Re:ZFS 2.3.0 released with ZFS raidz expansion
by ryao on Tuesday January 14, 2025 @04:02AM
(#42695197)
I forgot we still did not have that last bit implemented. However, it is less important now that we have expansion.
Re:ZFS 2.3.0 released with ZFS raidz expansion
by justinclift on Wednesday January 15, 2025 @01:06AM
(#42707851)
> 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.
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.