Lazy is not the goal, nor is prematurely cleaning out the bug tracker. After the 2019-12-04 message, it seemed that things were working well, so it seemed to be time for a re-declaration of what we are trying to achieve.
It seems this situation was created by a user explicitly running "zfs set dnodesize=auto" or a "zpool create -O dnodesize=auto ..." then trying to send to a dataset that doesn't support large dnodes. The default dataset property is 'legacy'. This is not caused by the pool's "feature@large_dnode" being "enabled", but it being set to "active" because a dataset was told explicitly to use the feature. It takes effort beyond defaults to get into this situation. When using ZFS on Linux is used as a receiver, "cannot receive new filesystem stream: pool must be upgraded to receive this stream", is the error message, which seem more appropriate (tested both 0.7.9 and 0.8.2). The poor error messages experienced in the bug report are due to using FreeBSD's "zfs receive" command, not the ZOL's "zfs send". It would seem that the error message correction needs to be done on the FreeBSD side. There is a project underway called ZFS on FreeBSD (ZOF). It ultimately will allow FreeBSD to compile from the same codebase as ZOL. If it isn't fixed in the current FreeBSD development, it will be incorporated then. That being said, there are feature flags, when enabled and activated by default, would prevent someone from importing the pool's disks using FreeBSD (vs. this bug's send/recv issue). Again, this may get fixed with ZOF, as it is utilized on FreeBSD machines. It would take a new ZFS version to be deployed on FreeBSD. This also occurs if a pool in made on a newer version of ZOL and an imported on a older, less capable version of ZOL. Though cross importing a pool to another OS (or older edition of ZOL) is an semi-advanced scenario, and the mentioned feature matrix would benefit those users. As these are advanced scenarios, I don't know if or when user education should be done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854982 Title: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1854982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs