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 Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1854982 Title: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0 Status in zfs-linux package in Ubuntu: New Bug description: After I tried to back-up my datapools from Ubuntu 19.10 to FreeBSD 12.0 as I have done since June each week, I found out it did not work anymore. The regression occurred after I reinstalled Ubuntu on my new nvme drive. I also had to reorganize my own datapools/datasets, because they either moved to the nvme drive or they had to be located on 2 HDDs instead of 3. I had one datapool that still works, the datapool containing my archives and it is the datapool, that has NOT been reorganized. I tried for a whole long day to get the backup working again, but I failed. I compared the properties from datapool and dataset, but did not see any problem there. Only a lot of new features and properties not present before and not present in FreeBSD. I used FreeBSD, because I use for backup an old 32-bits Pentium. I have two complaints: - the Ubuntu upgrade did cost me the compatibility with FreeBSD. Open-ZFS? :( - the system transfers the dataset and at the end of a long transfer it decides to quit and the error messages are completely useless and self contradicting. On the first try it say the dataset does exist and on the second try it says it does NOT exist. One of the two is completely wrong. Some consistency and some clearer error messages would be helpful for the user. See the following set of strange set error messages on two tries: root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | ssh 192.168.1.100 zfs receive zroot/hp-data/dummy cannot receive new filesystem stream: destination 'zroot/hp-data/dummy' exists must specify -F to overwrite it root@VM-Host-Ryzen:/home/bertadmin# /sbin/zfs send -c dpool/dummy@191130 | ssh 192.168.1.100 zfs receive -F zroot/hp-data/dummy cannot receive new filesystem stream: dataset does not exist A 2nd subset of my backup is stored on the laptop and that still works. I also compared the properties with those of my laptop, that still has its original datapools of begin of the year. I aligned the properties of FreeBSD with those of my laptop, but it did not help. I attach the properties of the datapool and dataset from both FreeBSD and Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zfsutils-linux 0.8.1-1ubuntu14.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 3 13:35:08 2019 InstallationDate: Installed on 2019-11-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1854982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
