[Bug 1880869] Re: Use persistent device name for vdevs
Jean-Baptiste Lallement
1880869 at bugs.launchpad.net
Wed Jun 24 14:11:25 UTC 2020
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * ZFS pools were created with device names such as /dev/sdX,
+ /dev/vdX,... However, these names are not stable and may change on each
+ reboot, leading to an unbootable system.
- * 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.
+ * "zpool create" now uses persistent device names with PARTUUID
+ instead.
[Test Case]
- * detailed instructions how to reproduce the bug
-
- * these should allow someone who is not familiar with the affected
- package to reproduce the bug and verify that the updated package fixes
- the problem.
+ * detailed instructions how to reproduce the bug
[Regression Potential]
- * discussion of how regressions are most likely to manifest as a result
- of this change.
-
- * It is assumed that any SRU candidate patch is well-tested before
- upload and has a low overall risk of regression, but it's important
- to make the effort to think about what ''could'' happen in the
- event of a regression.
-
- * This both shows the SRU team that the risks have been considered,
- and provides guidance to testers in regression-testing the SRU.
+ * Likely low risk of regression. Worst case system doesn't boot after a
+ fresh installation which is better than today because the system may
+ boot but subsequent boots may not.
[Other Info]
-
- * Anything else you think is useful to include
- * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
- * and address these questions in advance
+
+ * Already shipped in GRoovy
[Original Bug report]
ZFS pools are currently created with device names such as /dev/sdX, /dev/vdX,... However, this name is not stable and may change on each reboot.
"zpool create" must use persistent device names like UUID or PARTUUID instead.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu36
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 27 13:52:13 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss
InstallationDate: Installed on 2014-07-15 (2143 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to groovy on 2018-03-24 (794 days ago)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1880869
Title:
Use persistent device name for vdevs
Status in ubiquity:
Unknown
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Focal:
Triaged
Bug description:
[Impact]
* ZFS pools were created with device names such as /dev/sdX,
/dev/vdX,... However, these names are not stable and may change on
each reboot, leading to an unbootable system.
* "zpool create" now uses persistent device names with PARTUUID
instead.
[Test Case]
* detailed instructions how to reproduce the bug
[Regression Potential]
* Likely low risk of regression. Worst case system doesn't boot after
a fresh installation which is better than today because the system may
boot but subsequent boots may not.
[Other Info]
* Already shipped in GRoovy
[Original Bug report]
ZFS pools are currently created with device names such as /dev/sdX, /dev/vdX,... However, this name is not stable and may change on each reboot.
"zpool create" must use persistent device names like UUID or PARTUUID instead.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu36
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 27 13:52:13 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss
InstallationDate: Installed on 2014-07-15 (2143 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to groovy on 2018-03-24 (794 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubiquity/+bug/1880869/+subscriptions
More information about the foundations-bugs
mailing list