So these pools were created with the Ubuntu Ubiquity ZFS installer? I missed that because the pool names are hardcoded to bpool and rpool and your message lists 'dpool/dummy' and 'zroot/hp-data/dummy'
Also, in the linked email thread, you stated "The ZFS manual advised auto, if also using xattr=sa, so that is why I used auto for my own datapools/datasets." Now the origin of the pool is clearer to me. Yes I do see -O dnodesize=auto being set on (and inherited from) rpool in Ubiquity root zfs installation. This would impact the ease of sending to non- large_dnode pools (or in your case FreeBSD with large_dnode problems). Some simple tests to run: Within FreeBSD, I'd be really surprised if large_dnode=active to large_dnode=enabled/active zfs send/recv doesn't work, but I'd start there. Next, I'd try to send from FreeBSD large_dnode=active to Linux large_dnode=enabled/active. If it fails, what error is returned? Also, like rlaager stated, we should do the original Linux large_dnode=active to FreeBSD large_dnode=enabled/active that gave you problems. This all will give us evidence for bug reports in FreeBSD and/or ZOL upstreams. I'm on a mobile device, so can build examples, if requested, at a later time. -- 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
