Well, there's a few different kinds of "real fix". My message is mostly about trying to get our users to an upgrade path that works with a minimum of fuss.
The upstream OpenZFS developers have never supported different versions of userland utilities than the kernel modules. It's just happened to work fine for years because most people reboot into matching kernel modules shortly after they install new userland utilities and don't exhaustively stress the entire user-to-kernel communication in that window. But our scripts are doing something that exposes a mismatch. Probably the OpenZFS developers didn't expect our scripts to use this functionality in the moments between installing the utilities and rebooting into the new kernel modules. Fully addressing backwards and forwards compatibility in both the zfs kernel modules and the zfs userland utilities is probably expensive enough that nobody will ever do it. (If it were cheap and easy, surely someone would have done it.) Projects have to prioritize what they can work on with the resources that they have -- on-disk compatibility is far more important to the OpenZFS developers than backwards and forwards compatibility on the command and control channel. Yes, a full fix would be nice, but I expect it'll take far more resources than I can contribute, and probably more than Canonical can contribute. But we can probably figure out a way to get people past this hurdle, it just might take a while. I guess it's possible that whatever change broke the compatibility could also be found and reverted, but that'd just re-introduce the problem for whoever had already dealt with the problem. Depending upon how many people are affected, it might or might not make sense to revert the change and deal with the fallout of a *second* break. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110891 Title: System freeze on release upgrade 24.10 oracular to 25.04 plucky with root fs on ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2110891/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
