Erin wrote:
> The issue that we have is that the first two vdevs were almost full, so we
> will quickly be in the state where all writes will be on the 3rd vdev. It
> would
> also be useful to have better read performance, but I figured that solving the
> write performance optimization would also
> All new writes will be spread across the 3 vdevs. Existing data stays where it
> is for reading, but if you update it, those writes will be balanced across
> all 3
> vdevs. If you are mostly concerned with write performance, you don't have to
> do
> anything.
>
> Regards,
> Eric
The issue tha
Erin wrote:
> How do we spread the data that is stored on the first two raidz2 devices
> across all three so that when we continue to write data to the storage pool,
> we will get the added performance of writing to all three devices instead of
> just the empty new one?
All new writes will be spre
We had an existing zfs storage pool comprised of 2 raidz2 devices (or arrays)
and we just added a 3rd raidz2 device of equal size to the first two. While
making use of the extra capacity is mindlessly simple, we also want to take
advantage of the performance benefits.
How do we spread the data
