i've got most 'warnings' from tickets or forum threads accumulated until the pool blew up with 'blkptr has invalid TYPE' panic on import (so no longer on just disfunctional replication). from there, another UI error similar to this
sad story happened and UI reshuffled drives and geli assignments and wiped another pool. both pools replicated to each other, so the incredible 2 separate drive "backup" on top of RAID was instantly gone. UPS, selfpowered drives, ECC, none of this will save you from bugs. (actually trying to recall when a filesystem crashed a machine in last 30years and cannot, perhaps only a bad sector could crash widows3.11 in 90s?).
i have yet another backup as my setup was only 90% done, but not so well organised, months of work is gone, so i moved to hated BTRFS hoping their send/receive functions work and will jump on the ship once native encryption ZFS is ready and replication issues are finally recognized, instead of blaming everyones hardware. 11.3 will likely stay in this shape given the priority of tickets, i'm looking forward for
v13 looking at, citing, "create a culture of testing" (yes please!), "Forwarding: 100gbps" (yes, let's abandon this slow 10gbit) and zfs persistent arc, native encr etc.