petr
Contributor
- Joined
- Jun 13, 2013
- Messages
- 142
Hello!
One of my pools is running with a single RAIDZ2 vdev. I am considering extension by adding another, identical RAIDZ2 vdev into the pool - which I understand can be done easily.
In documentation, I've found that pool will stripe the data across all vdevs when they are there since the creation of the pool. My question is - what happens when the vdev is added later? The pool in question is approaching 80% now. Would a simple removal and copying back of larger files "force" the stripe or how does the internal scheduling work? Is there a way to let it "reshuffle" itself to fill the 2 vdevs evenly with data to maximise performance?
One of my pools is running with a single RAIDZ2 vdev. I am considering extension by adding another, identical RAIDZ2 vdev into the pool - which I understand can be done easily.
In documentation, I've found that pool will stripe the data across all vdevs when they are there since the creation of the pool. My question is - what happens when the vdev is added later? The pool in question is approaching 80% now. Would a simple removal and copying back of larger files "force" the stripe or how does the internal scheduling work? Is there a way to let it "reshuffle" itself to fill the 2 vdevs evenly with data to maximise performance?