OK, thank you, that solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852793
Title:
Various problems related to "zfs mount -a
To manage notifications about this bug go to:
https://
** Description changed:
I boot from ZFS since the begin of the year. I have a multi-boot situation
with:
- Ubuntu 19.10 with Virtualbox booting from ZFS
- - Ubuntu Mate 19.10 with QEMO/KVM booting from ZFS
+ - Ubuntu Mate 19.10 with QEMU/KVM booting from ZFS
- Ubuntu 19.10 booting from ext4
> I think "zfs mount -a" should NOT try to mount datasets with
> mountpoint "/"
There is no need for this to be (confusingly, IMHO) special-cased in
zpool mount.
You should set canmount=noauto on your root filesystems (the ones with
mountpoint=/). The initramfs handles mounting the selected root
** Description changed:
I boot from ZFS since the begin of the year. I have a multi-boot situation
with:
- Ubuntu 19.10 with Virtualbox booting from ZFS
- Ubuntu Mate 19.10 with QEMO/KVM booting from ZFS
- Ubuntu 19.10 booting from ext4
I have two problems with zfs:
- the last upda
