jenksdrummer
Patron
- Joined
- Jun 7, 2011
- Messages
- 250
Earlier when I built my pool I didn't think anything of it and created it with 6 mirrored vdevs; a mirrored metadata vdev, a single cache, and a mirrored log vdev. World was happy, etc.
As I got to rebuild that pool due to a dataset removal causing a panic/reboot, I thought I'd see what performance is like with a pair of Z2 vdevs this time around, and the rest being of the same allocations; and I got the warning about the vdev topology not being right. I can force it, it seems, but thought I'd pose the question "why" they need to match; to what reason would there be to have a requirement Z2 metadata vdev? (else risk being an unsupported configuration) - I understand the need for redundancy as the pool surviving a failure would be dependent on that redundancy (unlike cache vdev; as that's a read cache, not a write cache)
Anyway, thanks!
As I got to rebuild that pool due to a dataset removal causing a panic/reboot, I thought I'd see what performance is like with a pair of Z2 vdevs this time around, and the rest being of the same allocations; and I got the warning about the vdev topology not being right. I can force it, it seems, but thought I'd pose the question "why" they need to match; to what reason would there be to have a requirement Z2 metadata vdev? (else risk being an unsupported configuration) - I understand the need for redundancy as the pool surviving a failure would be dependent on that redundancy (unlike cache vdev; as that's a read cache, not a write cache)
Anyway, thanks!