ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
Bug #1685528 reported by
Sam Van den Eynde
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zfs-linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Per https:/
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.
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 /github. com/zfsonlinux/ pkg-zfs/ issues/ 221
https:/
[1] https:/ /bugs.launchpad .net/ubuntu/ +source/ zfs-linux/ +bug/1550301
--
Richard