Comment 69 for bug 2044657

@Dimitri If I see it correctly you have been assigned this bug. So I thought this should be your decision!? If not this is bad, who is responsible then for the rejection of this? Whoever made that decision obviously didn´t follow close enough what was going on in the zfs GitHub repo regarding this bug and the multiple raised issues.

I honestly don't get it how this important fixes ending up in 2.2.2 needed over 2 months and then don't make it to a decent solution in Ubuntu. Almost every relevant distribution had that fixed fast and of course went with 2.2.2 having the trust in the ZFS devs in knowing what they are fixing. (Well I know that all raised from a bug in the zfs repo in the first place, but that one was quite complex.)

So I can just ask again everyone involved in this decision to rethink this and go with 2.2.2 for mantic. Please don´t waste 2 months with cherry picking and brewing own solutions when the house is burning on a central part of the OS as the filesystem. This should have been a hotfix in the first place.