public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rescue cd for zfs 2.1 or thereabouts
Date: Mon, 23 Aug 2021 14:02:29 -0400	[thread overview]
Message-ID: <CAGfcS_noTcvZqJP=zr85ZN0r9XKd3zpnG+r4=2RugJ+MiBtyDw@mail.gmail.com> (raw)
In-Reply-To: <20210823185739.14936fbb@digimed.co.uk>

On Mon, Aug 23, 2021 at 1:57 PM Neil Bothwick <neil@digimed.co.uk> wrote:
>
> On Mon, 23 Aug 2021 13:37:01 -0400, Rich Freeman wrote:
>
> > > Your root pool setup doesn't really matter for GRUB compatibility.
> > > What's important is that you have the proper features setup on your
> > > boot pool. That's the one GRUB loads.
> >
> > Sure, and in this case /boot is on my root pool.
> >
> > In any case, it would be nice if there was some way to tell what zpool
> > features grub requires, as it is a limiting factor for whatever pool
> > /boot happens to be on.
>
> Aren't new features only applied to newly created pools and datasets? If
> /boot was compatible with GRUB it should still be. At least that's how I
> read the einfo messages zfs spits out.

That is correct.  I want to know when I can enable the new features.
Of course, it would also be nice to know which features must be
disabled when creating a new boot pool.

It is just frustrating that as far as I can tell, there is no
documentation about what features grub supports.  It wouldn't be hard
for them to just say "here are the zpool features known to work in
grub version foo."  The best I've found is the Arch wiki, which has
the disclaimer that it is probably out of date and to check the man
pages, but of course the man pages don't actually say anything.

-- 
Rich


  reply	other threads:[~2021-08-23 18:02 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 15:45 [gentoo-user] rescue cd for zfs 2.1 or thereabouts Vitor Hugo Nunes dos Santos
2021-08-23 17:37 ` Rich Freeman
2021-08-23 17:57   ` Neil Bothwick
2021-08-23 18:02     ` Rich Freeman [this message]
2021-08-23 18:13       ` Neil Bothwick
2021-08-23 18:29         ` Rich Freeman
2021-08-23 19:50         ` Vitor Hugo Nunes dos Santos
2021-08-23 20:13           ` Neil Bothwick
2021-08-23 20:21           ` Vitor Hugo Nunes dos Santos
2021-08-23 20:13         ` Vitor Hugo Nunes dos Santos
2021-08-23 20:57         ` John Covici
2021-08-23 21:21           ` Neil Bothwick
2021-08-24  6:57             ` John Covici
2021-08-24  7:33               ` Neil Bothwick
  -- strict thread matches above, loose matches on Subject: below --
2021-08-23  9:49 Vitor Hugo Nunes dos Santos
2021-08-23  8:15 John Covici
2021-08-23  9:51 ` Miles Malone
2021-08-23 12:13   ` John Covici
2021-08-23 13:52     ` Rich Freeman
2021-08-23 14:13       ` John Covici
2021-08-23 14:24         ` Rich Freeman
2021-08-23 15:11 ` Neil Bothwick
2021-08-23 15:24   ` Rich Freeman
2021-08-23 17:38 ` Meik Frischke
2021-08-23 21:01   ` John Covici
2021-08-31 11:11 ` Robert David
2021-08-31 13:33   ` John Covici
2021-08-31 14:04     ` Rich Freeman
2021-08-31 14:33       ` Matt Connell (Gmail)
2021-08-31 17:51         ` Michael
2021-08-31 18:21           ` Rich Freeman
2021-08-31 19:21             ` Neil Bothwick
2021-08-31 19:44               ` Michael
2021-08-31 19:54                 ` Rich Freeman
2021-08-31 20:20                   ` Michael
2021-08-31 20:42                     ` Jack
2021-08-31 21:09                 ` Neil Bothwick
2021-08-31 15:02     ` Neil Bothwick

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='CAGfcS_noTcvZqJP=zr85ZN0r9XKd3zpnG+r4=2RugJ+MiBtyDw@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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