You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature would like to see added to OpenZFS
I'd really love a tool to locate any narrow stripes and rewrite them at the new stripe width after expansion has completed.
How will this feature improve OpenZFS?
RAIDZ expansion works by reordering the data on the drives; where existing data retains its original stripe width.
After expansion is complete, it may be desirable to reclaim disk space by rewriting old stripes at the new full stripe width.
There is no user-driven process to identify data written with the old stripe width and atomically rewrite the data with the new strip width. Work-arounds require copying data around the filesystem, they're not atomic, they also affect the file metadata/timestamps, etc.
The text was updated successfully, but these errors were encountered:
If ZFS could do this, it would mean that it has to rewrite all data on the expanded vdev. A better way would be to implement a raid-dp like raid model. In the raid-dp model, you can add everytime drives to an existing raid group without the need to rewrite everything. This is possible, because you have separate parity drives like raid-4.
If ZFS could do this, it would mean that it has to rewrite all data on the expanded vdev.
Yes, it would. That's exactly the goal. A better way might be to do it while expanding, but my understanding is that's not on the table; the expansion strategy was chosen because it's extremely safe and simple... (?)
Describe the feature would like to see added to OpenZFS
I'd really love a tool to locate any narrow stripes and rewrite them at the new stripe width after expansion has completed.
How will this feature improve OpenZFS?
RAIDZ expansion works by reordering the data on the drives; where existing data retains its original stripe width.
After expansion is complete, it may be desirable to reclaim disk space by rewriting old stripes at the new full stripe width.
There is no user-driven process to identify data written with the old stripe width and atomically rewrite the data with the new strip width. Work-arounds require copying data around the filesystem, they're not atomic, they also affect the file metadata/timestamps, etc.
The text was updated successfully, but these errors were encountered: