** 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 update of zfs failed, because the dataset "/" was not empty. Of course it was not empty, it contained the second OS e.g. Ubuntu Mate. - during startup my datapools were not mounted, that is a regression, since approx a month I have that issue. Both I can solve by changing the mountpoint for the other system from "/" to e.g. "/systems/roots/mate". Afterwards the update has been executed without problems and the system rebooted with the datapools mounted as expected. - I think "zfs mount -a" should NOT try to mount datasets with mountpoint - "/", except their own system or change the error into a warning and - continue the mount process. + I think "zfs mount -a" should either + - NOT try to mount datasets with mountpoint "/", except their own system or + - change the error into a warning and continue the mount process or + - set the mountpoints in /boot/grub.cfg by changing etc/grub.d/10_linux_zfs. The advantage of the last one is, that the other OS is accessible by a file manager, exactly like in ext4 multi-boot situations.
-- 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/1852793 Title: Various problems related to "zfs mount -a Status in zfs-linux package in Ubuntu: Invalid Bug description: 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 QEMU/KVM booting from ZFS - Ubuntu 19.10 booting from ext4 I have two problems with zfs: - the last update of zfs failed, because the dataset "/" was not empty. Of course it was not empty, it contained the second OS e.g. Ubuntu Mate. - during startup my datapools were not mounted, that is a regression, since approx a month I have that issue. Both I can solve by changing the mountpoint for the other system from "/" to e.g. "/systems/roots/mate". Afterwards the update has been executed without problems and the system rebooted with the datapools mounted as expected. I think "zfs mount -a" should either - NOT try to mount datasets with mountpoint "/", except their own system or - change the error into a warning and continue the mount process or - set the mountpoints in /boot/grub.cfg by changing etc/grub.d/10_linux_zfs. The advantage of the last one is, that the other OS is accessible by a file manager, exactly like in an ext4 multi-boot situations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852793/+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
