The size of the pool is not particularly relevant. It sounds like you
think I'm asking you to backup and restore your pool, which I definitely
am not. A pool "import" is somewhat like "mounting" a pool (though it's
not literally mounting, because mounting is something that happens with
filesystems). An "export" is similarly like unmounting.

As I said, those instructions were intended to be a _safe_ way for you
to return your system to working order. It's likely not necessary to
boot into recovery mode, or export the pool to resolve this.

The key thing is that /vms and /hp-data are non-empty. Fix that and your
mounting issue will be resolved. I was suggesting you go into recovery
mode and export the data pool to avoid the potential for accidents. But
really, if you only use `rmdir` rather than `rm -rf`, you should be
safe.

Root-on-ZFS installs are not supported by Ubuntu or Canonical. Canonical
is working on providing experimental support for Root-on-ZFS in the
installer for 19.10, which should be out this month.

I do not work for Canonical. I provide the upstream ZFS-on-Linux Root-
on-ZFS HOWTOs for Debian and Ubuntu as a volunteer project. I have never
guaranteed any in-place upgrade path. And you likely didn't follow my
HOWTO anyway, as your dataset naming and mount properties don't match
those from the HOWTO.

I certainly agree that this is fragile. But it's an unofficial,
experimental setup. That comes with the territory. Important progress is
being made, and this will hopefully be more robust in the future.

-- 
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