- Nov 4, 2018
I'll quibble about "prevent such configurations entirely" - "zpool create raidz2 poolname dev1 ... devN" is still a thing. Anyone who runs that from CLI clearly meant to do that, whatever the (sub-optimal) outcome.I guess that depends on how you define "bug." It's probably behaving as intended, but "as intended" is, well, not very good behavior. The pool configuration @kivalo is considering is not optimal or recommended, but that doesn't mean it's always a bad idea, and to prevent such configurations entirely with no possibility of bypassing the warnings doesn't seem like a very good idea--particularly when every previous version of FreeNAS has allowed for this (after appropriate warnings).
Without knowing how many people inadvertently, and warnings notwithstanding, created a vdev configuration they didn't mean to create, it's hard to make a judgment call on whether the pros of this change - keeps GUI users from shooting themselves in the foot - outweigh the cons: Need to drop to CLI to create mixed-disk-size vdevs.