Comment 7 for bug 1939210

I feel like this is a subject that needs to be resolved.

Recently when I tried using zfs send and receive from ubuntu to a fresh install of ubuntu 20.04.3 LTS.
I could 'ten receive the dataset properly.

After looking at the net I discovered that the ZFS kmod and User tools didn’t match.
Because this fresh install of Ubuntu 20.04.3 had HWE kernel by default and that meant the ZFS kmod and user tools In the LTS repository didn’t match.

According to OpenZFS github this is a very bad thing.

Basically when one chooses an Ubuntu LTS. Its because it is the stable version of ubuntu with no breaking changes.
Making HWE kernel be the default does the exact opposite of this and actually makes a breaking change to ZFS and that is exactly what is not supposed to happen.

But for some reason canonical is overlooking this on ZFS where people store there important files.

This is still a breaking change and in the future it could potentially lead to data loss which would cause a huge uproar when people start loosing their files because a new kernel had a kmod that didn’t match the user space tools in the repositories.

I really feel like canonical should have a look at this and understand this does exactly what it is not supposed to do on an LTS. It gives breaking changes by having the HWE kernel pr. default and not having the option to use a matching ZFS user tools In their repo.

In the end I manually had to install Linux-image-generic and accompanying modules, modules-extra and headers packages.
Then remove anything related to HWE kernel to make sure I never booted on the wrong kernel with the mismatching kmod/userspace of zfs.

And after that I had no ZFS send/receive problems

I would just wish I could get a corresponding zfsutils-linux that matches the HWE kernel so that I can stay on the latest kernel without breaking ZFS.