Hello Folks,
I think I experienced this bug upgrading Ubuntu from 18.04 > 20.04 last
night. If not, apologies.
I have the OS running on USB drive, normal install with all my data in a
ZFS pool. After roboot/upgrade completed my ZFS pool is no longer
listed.
Not a ZFS guru so nervous of next
This bug was fixed in the package ubiquity - 20.04.15.1
---
ubiquity (20.04.15.1) focal; urgency=medium
[ Sebastien Bacher ]
* debian/real-po: updated translations from launchpad, including strings
from the new subpage for RST (LP: #1874103)
[ Michael Hudson-Doyle ]
*
SRU verification for Focal:
I have reproduced the problem with ubiquity 20.04.15 in focal and have verified
that the version of ubiquity 20.04.15.1 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added:
Hello Saverio, or anyone else affected,
Accepted ubiquity into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ubiquity/20.04.15.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: ubiquity (Ubuntu Focal)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu Focal)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875045
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * Ubiquity unmounts everything that could be mounted on the target file
+ system when it starts and on tear down. For ZFS it exports all the
+ pools.
- * justification for backporting the fix
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
This bug was fixed in the package ubiquity - 20.10.2
---
ubiquity (20.10.2) groovy; urgency=medium
[ Jean-Baptiste Lallement ]
* zsys-setup: Use persistent device name for vdevs (LP: #1880869)
* Only export pools created during installation and containing dataset
mounted
> Regarding your other issue, it is possible that using /dev/sdX for vdev
> causes it. Depending on the type of block device these names are not
> stable and may change on boot or when udev runs. It's more reliable to
> use /dev/disk/by-uuid or /dev/disk/by-partuuid which are persistent.
I think
** Changed in: ubiquity (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875045
Title:
Ubiquity 20.04 exports existing ZFS pools
To manage
** Merge proposal linked:
https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity-1/+merge/384701
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875045
Title:
Ubiquity 20.04 exports existing
I'm working on a patch to only unmount pools that we've mounted as part
of the installation to prevent unmounting pools that don't belong to us.
Regarding your other issue, it is possible that using /dev/sdX for vdev
causes it. Depending on the type of block device these names are not
stable and
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875045
Title:
Ubiquity 20.04 exports existing ZFS
Something odd is going on, which I don't know if it's expected or not,
as Ubiquity may be intentionally messing with udev.
Specifically, if I have zvols, and run Ubiquity (which exports them),
once I reimport the pool, the zvols have the block devices swapped. I
can reproduce this all the time,
** Changed in: ubiquity (Ubuntu)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875045
Title:
** Summary changed:
- Ubiquity 20.04 interferes with existing ZFS pools, making them "disappear"
+ Ubiquity 20.04 exports existing ZFS pools
** Description changed:
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04
- interferes with existing ZFS pools, making them
16 matches
Mail list logo