I updated both Ubuntu and I upgrade FreeBSD to 12.1, but it did not help. Both system remain incompatible.
So what should we learn: - Never break the send/receive compatibility, especially not if you demand during the install the complete disk (Ubuntu) or all complete disks (Raid-0 or 1) (FreeBSD). The minimum improvement I expect for the 20.04 installation, is one size parameter! So that I can limit the part of the disk used by Ubuntu itself (ext4 partition + swap partition + bpool + rpool). For Ubuntu it is like installing on a smaller disk. At least the remainder of the disk could be used to create own datapools with the correct feature settings. - ZFS should give useful not conflicting error messages as explained in my first entry. In the mean time I have to; - backup my dpool (normal files) on my HDDs an recreate dpool with the correct feature set; - restore those normal files to dpool and run the send/receive backup to FreeBSD; - copy my VMs temporarily to that new dpool and delete those datasets on rpool. - snapshot all Ubuntu datasets and send/receive those to an USB drive. - boot from ext4, I'm lucky I have a dual boot with ext4 and zfs. - delete rpool, create a new 20GB rpool version and reverse send/receive Ubuntu from USB to rpool - check UUIDs in /boot/grub/grub.cfg, fstab and resume; reboot and pray - recreate a vpool for the virtual machines with the right feature set and restore those. - run the backup to FreeBSD. My laptop has already large-dnode active as result of an incremental backup, so I have to recreate that datapool too with the right feature set. As last resort I take my last free SATA HDD (80GB) from my 2nd desktop and install Ubuntu on it and use the 512GB NVME SSD for my virtual machines. That Ubuntu Host OS is a minimal install and I only use Firefox, nautilus, the terminal and gedit from it. In practice the Host OS will run completely from L1ARC, surely if I use Firefox from the VMs like I do often. -- 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
