From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] zfs 0.8.3_2, linux5.5 may fail to boot with encryption (tracking issue)
Date: Tue, 07 Apr 2020 17:29:10 +0200 [thread overview]
Message-ID: <20200407152910.rItc82D8rGCVhmUPRayxSSU6FG2qzNiVteyxXG8dOVk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20711@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Closed issue by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/20711
Description:
I'm creating this issue to document and track a potential incompatibility between `zfs-0.8.3_2`, `linux5.5` and encryption. On the `#voidlinux` IRC channel, user `w1kl4s` reported that a system with an unencrypted boot partition and an encrypted root fails to boot `linux5.5` with `zfs-0.8.3_2` and `zfsbootmenu`, although the same problem reportedly affects a system using `rEFInd` without `zfsbootmenu`.
@zdykstra may be able to reproduce this issue and provide more insight. I do not use encyrption with ZFS but have no issues booting current `linux5.4`, `linux5.5` or `linux5.6` kernels using `zfs-0.8.3_2`.
Note that ZFS 0.8.3 does not officially support any kernel above Linux 5.4. The patch applied in Void package `zfs-0.8.3_2` to support `linux5.6` is a backport of patches accepted upstream to support Linux 5.6 (the patch file in the tree references the upstream issue) while we wait for a new ZFS point release or OpenZFS 2.0.
Hopefully, we can reproduce the issue and determine whether this problem appears upstream or only in the backported patch.
next prev parent reply other threads:[~2020-04-07 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 0:35 [ISSUE] " ahesford
2020-04-07 3:02 ` ahesford
2020-04-07 15:29 ` ahesford
2020-04-07 15:29 ` ahesford [this message]
2020-04-07 15:29 ` ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200407152910.rItc82D8rGCVhmUPRayxSSU6FG2qzNiVteyxXG8dOVk@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).