Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ZFS 2.1.5_1 breaks boot on non zfs-on-root systems
Date: Thu, 30 Jun 2022 23:30:06 +0200	[thread overview]
Message-ID: <20220630213006.O2zqXuangjZYaG-89hTZf6HxZUbXy9_QH2yEkvkvpr0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37667@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 783 bytes --]

Closed issue by adrian-bl on void-packages repository

https://github.com/void-linux/void-packages/issues/37667

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.4_1 x86_64 GenuineIntel uptodate rFFF

### Package(s) Affected

zfs-2.1.5_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The system boots

### Actual behaviour

After upgrading 2 systems from ZFS 2.1.4 to 2.1.5, both systems fail to boot as dracut complains about not being able to mount the rootfs.

Note that ZFS is *not* used as rootfs: one system uses ext4, the other btrfs.

### Steps to reproduce

1. Have a non root-on-zfs system
2. Install zfs-2.1.5_1
3. Reboot -> system will fail to startup


  parent reply	other threads:[~2022-06-30 21:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 10:45 [ISSUE] " adrian-bl
2022-06-24 10:47 ` adrian-bl
2022-06-24 13:53 ` zdykstra
2022-06-24 13:54 ` ahesford
2022-06-24 14:19 ` adrian-bl
2022-06-24 14:22 ` adrian-bl
2022-06-24 15:31 ` ahesford
2022-06-24 16:25 ` Vaelatern
2022-06-24 16:41 ` Vaelatern
2022-06-30 21:30 ` ahesford [this message]
2022-06-30 21:30 ` ahesford
2022-07-01  5:01 ` adrian-bl
2022-07-01 23:49 ` aaFn
2022-07-02  2:33 ` RunningDroid
2022-07-02 10:11 ` aaFn

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=20220630213006.O2zqXuangjZYaG-89hTZf6HxZUbXy9_QH2yEkvkvpr0@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).