In module/os/freebsd/zfs/zvol.c, the zv_volblocksize member never gets set in a zvol's state. Notably, this causes indirect writes to enter an infinite loop allocating memory until all available RAM is wired and the starved system becomes unresponsive. Surely other code paths suffer as well.
An easy way to hit the indirect write code path is to create a zvol with logbias=throughput and try to write something to it.
In module/os/freebsd/zfs/zvol.c, the zv_volblocksize member never gets set in a zvol's state. Notably, this causes indirect writes to enter an infinite loop allocating memory until all available RAM is wired and the starved system becomes unresponsive. Surely other code paths suffer as well.
An easy way to hit the indirect write code path is to create a zvol with logbias=throughput and try to write something to it.