To add to Jonathan's comment, a slightly easier way to do this (at least for someone not familiar with bootloaders) is to add `options zfs zfs_dmu_offset_next_sync=0` to /etc/modprobe.d/zfs.conf
On a side note, I'd like to second the concerns about cherry-picking. Given that the bug was originally introduced due to a combination of changes introduced in 2.1 and the pre-existing issue, I'm worried that backporting a fix can introduce its own issues and won't have the same degree of testing and community support as the upstream 2.2.2.
To add to Jonathan's comment, a slightly easier way to do this (at least for someone not familiar with bootloaders) is to add `options zfs zfs_dmu_ offset_ next_sync= 0` to /etc/modprobe. d/zfs.conf
https:/ /openzfs. github. io/openzfs- docs/Performanc e%20and% 20Tuning/ Module% 20Parameters. html
On a side note, I'd like to second the concerns about cherry-picking. Given that the bug was originally introduced due to a combination of changes introduced in 2.1 and the pre-existing issue, I'm worried that backporting a fix can introduce its own issues and won't have the same degree of testing and community support as the upstream 2.2.2.