Fix released in Bionic.
** Changed in: zfs-linux (Ubuntu)
Status: Fix Committed => 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/1685528
Title:
ZFS initramfs mounts dataset
I fixed this upstream, which was released in 0.7.4. Bionic has 0.7.5.
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => 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/1685528
samvde, can you provide your `zfs list` output? The script seems
designed to only import filesystems *below* the filesystem that is the
root filesystem. In the typical case, the root filesystem is something
like rpool/ROOT/ubuntu. There typically shouldn't be children of
rpool/ROOT/ubuntu.
--
Hi Richard, I'll be happy to upload this fixes into the non-LTS releases
where this script is missing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685528
Title:
ZFS initramfs mounts dataset
Copying the script is probably fine for now. I still intend to look at
this, hopefully in the next month or so. It's been relatively low on my
list, since LTS releases are my main priority.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Are there any recommendations how to proceed with the EOL for yakkety
set? I use zfs clones as inpromptu boot environments when updating and
use ZFS datasets for docker and lxd, so I have a fair amount of
'canmount=none's and 'mountpoint=legacy's. I am reluctant to just c
the script from yakkety
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/1685528
Title:
I suspect that wouldn't work, for one reason or another. The upstream
one has more features, probably.
I'd rather just keep this Debian-specific. The initramfs script is
likely to have distro specific code. I don't see the idea of one unified
script working out well.
--
You received this bug
Can't we upstream the Xenial zfs script instead of fixing the "new" one?
It supports the same syntax, and does what it needs to do? And it does
not try to mount datasets I explicitly configured not to be mountable ;)
Seems like the faster solution, no?
--
You received this bug notification
It should not restrict import to hardcoded /dev and /dev/disk/by-id -
see https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685528
Title:
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685528
Title:
ZFS initramfs mounts dataset explicitly set not to be mounted, causing
boot process to fail
To
On 04/22/2017 12:36 PM, Sam Van den Eynde wrote:
> Experienced this with Ubuntu Zesty. Xenial seems to ship with a
> different zfs script for the initrd.
Who completely replaced the zfs-initramfs script?
Was there a particular reason for this massive change, and was it
discussed anywhere?
This
12 matches
Mail list logo
