I'm not sure who to create corruption, but I have plenty of it causing processes to kernel panic. https://github.com/openzfs/zfs/issues/11474 contains some instructions on how to create a corrupted file using wine.
Even after this fixed zfs hits, those of us with scrambled file systems are going to need help in clearing out the mess :( So please don't close this bug until there is a mitigation process as well as a fix to zfs to stop it happening further.
Does using an encrypted pool have any impact on this?
Actually zfs-2.0.2-1ubuntu5, zfs-kmod- 2.0.3-8ubuntu5.
I'm not sure who to create corruption, but I have plenty of it causing processes to kernel panic. https:/ /github. com/openzfs/ zfs/issues/ 11474 contains some instructions on how to create a corrupted file using wine.
Even after this fixed zfs hits, those of us with scrambled file systems are going to need help in clearing out the mess :( So please don't close this bug until there is a mitigation process as well as a fix to zfs to stop it happening further.
Does using an encrypted pool have any impact on this?