My mistake it should be confirmed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571241
Title:
ZFS initrd script does not import zpool using /dev/disk/by-id device
paths
To manage
** Changed in: zfs-linux (Ubuntu Xenial)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571241
Title:
ZFS initrd script does not import zpool using
** Changed in: zfs-linux (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571241
Title:
ZFS initrd script does not import zpool using /dev/disk/by-id
** Also affects: zfs-linux (Ubuntu Yakkety)
Importance: Undecided
Status: Fix Released
** Also affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571241
Title:
ZFS initrd script does not import zpool using /dev/disk/by-id
No errors encountered using the PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571241
Title:
ZFS initrd script does not import zpool using /dev/disk/by-id device
paths
To manage
@svde-tech: Can you please test from this PPA:
https://launchpad.net/~rlaager/+archive/ubuntu/zfs
Here's what I think should happen. Right now, you're seeing /dev/sdX
names. If you reboot with this package, you'll still see /dev/sdX names.
Reboot again and edit your GRUB command line (at boot,
The upstream fix has been committed for 0.6.5.7:
https://github.com/zfsonlinux/zfs/commit/325414e483a7858c1d10fb30cefe5749207098f4
At this point, Ubuntu could accept my debdiff in comment #11, or wait
for 0.6.5.7.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Attached is a backport of the fix from upstream. If I have a pool which
was last imported using /dev/disk/by-id names, the patch causes zpool
import to import it using /dev/disk/by-id names.
Note that this fix has not yet been merged upstream.
Also, note that the patch did not apply *perfectly*
The attachment "A patch (but note the design question here)." seems to
be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
I agree that the solution by-id should not be hard coded, this was
merely for testing purposes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571241
Title:
ZFS initrd script does not import zpool
/dev/disk/by-id isn't the only answer. Other people use other things, at
least in some cases. And I don't think that using /dev/disk/by-id as a
hard-coded default is acceptable. I'm pretty sure it's possible (though
rare) to have drives that show up in /dev, but not /dev/disk/by-id.
Richard Yao
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571241
Title:
Possible upstream bug report:
https://github.com/zfsonlinux/zfs/issues/3043#issuecomment-173677425
Another upstream bug report which has been closed due to Ubuntu's inclusion of
ZFS:
https://github.com/zfsonlinux/pkg-zfs/issues/148
--
You received this bug notification because you are a member
Your testing confirms this is not a regression (or at least not one
caused by my changes to the initramfs script), as I suspected. I am
still doing a plain zpool import just as it did before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Some additional tests.
If I add the zpool.cache (generated in Live environment to make sure it
has full by-id paths) to /etc/zfs, and replace the zfs script with the
one from 15.10 (/usr/share/initramfs-tools/scripts, requires initramfs
regeneration + changing grub boot parameters to include
I created the zpool.cache file using zpool set
cachefile=/etc/zfs/zpool.cache and recreated the initrd using update-
initramfs -c -k all without success.
Tried creating the zpool on the system itself, and then again using the
Live USB (since this shows by-id paths correctly). I double checked
It is a new install on zfs root. I created the pool using the by-id
names, and during my tests I have exported and re-imported it using the
by-id names as well. As this is a root filesystem, this obviously
happens from within a live environment so if the file got created, it
sure isn't on the
I'm away from my computer at the moment, or I'd test more myself. Did
you initially have the pool imported using the by-id names? Is the
problem that the initrd needs a zpool.cache file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
19 matches
Mail list logo
