[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: Fix Released Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: Fix Committed Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: Confirmed Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: Confirmed Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: Confirmed Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 over to zesty, but seriously short of better ideas. Cheers! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: Confirmed Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: Confirmed Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: New Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: New Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: New Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: New Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
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 change has caused many regressions, of varying importance. I realize I don't "own" this code, but as someone who is very involved in root-on-ZFS installs in Ubuntu, I'm quite annoyed that nobody asked me if this was a good idea or mentioned it was happening so I might review it and offer some feedback. Aside from the issue that Sam Van den Eynde is having [0], this also reverted a number of changes I made, including but not limited to: the support I added for rootdelay= and the code to set elevator=noop [1]. [0] https://bugs.launchpad.net/bugs/1685528 https://github.com/zfsonlinux/pkg-zfs/issues/221 [1] https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1550301 -- Richard ** Bug watch added: github.com/zfsonlinux/pkg-zfs/issues #221 https://github.com/zfsonlinux/pkg-zfs/issues/221 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: New Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp