I used the following commands on both systems;
sudo zpool export hp-data
sudo zfs list  # the other command produces a lot of snap mounts
sudo umount -l /vms/vms #the only other mounted dataset
sudo rmdir /hp-data
sudo rmdir /vms/vms
  Update and upgrade the system
sudo zpool import hp-data
sudo zfs mount -a

Afterwards the updated system worked again, but it only proves, that you have 
to umount(/rmdir?) all non-root datasets in the ZFS update procedure before 
starting the update itself. 
The same happened to my ext4 install and removing ZFS and reinstalling it 
solved the problem, so this is a bug that should be corrected. 

I do not think that rmdir has anything to do with the issue, I think
unmouting all non-root datasets solved the problem. In the ext4
installation I did not use rmdir. I just reinstalled ZFS and of course
the datasets were not yet mounted during the installation. I could
rollback one of the ZFS installations to the beta date and try out the
procedure without rmdir, but only if you think it is useful and a real
bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846424

Title:
  19.10 ZFS Update failed on 2019-10-02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to