The system uses xattr=sa, but I did not set it myself. Like you can see in the annex, it has been inherited from rpool everywhere and it has been set by the installer.
I annexed the properties - Home of Ubuntu, which properties I did not touch at all (except canmount) and - my main dataset with my VMs (rpool/vms/Vbox), where I only changed its dnodesize and snapdir. The last one (rpool/vms/Vbox) I backup weekly to FreeBSD 12.1. For my last try-outs I did use the Home directory of Ubuntu and that one failed. The only significant difference, I notice between the two datasets, is dnodesize. I made the .zfs folder visible this year to restore a VM. Remark: I use the experimental Ubuntu install with Root on ZFS, but I also have an ext4 installation on the PC, so I dual boot. Kind of last resort for the experimental install. In say October and November to be able to update ZFS on the ext4 installation, I had to change canmount during the update, but I think that bug has been solved. Canmount is back at its default. On Fri, 2020-01-31 at 13:24 +0000, Garrett Fields wrote: > I quickly set up a VM last night and tried to recreate problem, I > have > been unsuccessful so far. I'm wondering if certain dnode data > (perhaps > the use of xattr=sa on the Linux source) might be triggering the > issue? > ** Attachment added: "properties" https://bugs.launchpad.net/bugs/1854982/+attachment/5324493/+files/properties -- 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
