I'm planning to add a Metadata VDev to a pool in SCALE.
I note the following warning and see that the UI in SCALE requires the Metadata VDev to be the same structure as the Data VDev.
On CORE, I don't recall this decision being forced in the UI. On this SCALE pool, I had intended to add the Metadata VDev as a three-way mirror with the supposition that it's faster with similar data integrity to RAIDZ2. Am I wrong about this?
I'm fine to install a RAIDZ2, but if the three-way mirror is actually "better," I'd like to do that instead.
I note the following warning and see that the UI in SCALE requires the Metadata VDev to be the same structure as the Data VDev.
Using a Mirror layout is possible, but it is strongly recommended to keep the layout identical to the other vdevs. If the special vdev fails and there is no redundancy, the pool becomes corrupted and prevents access to stored data.
On CORE, I don't recall this decision being forced in the UI. On this SCALE pool, I had intended to add the Metadata VDev as a three-way mirror with the supposition that it's faster with similar data integrity to RAIDZ2. Am I wrong about this?
I'm fine to install a RAIDZ2, but if the three-way mirror is actually "better," I'd like to do that instead.