1 |
On Mon, Aug 23, 2021 at 1:57 PM Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> |
3 |
> On Mon, 23 Aug 2021 13:37:01 -0400, Rich Freeman wrote: |
4 |
> |
5 |
> > > Your root pool setup doesn't really matter for GRUB compatibility. |
6 |
> > > What's important is that you have the proper features setup on your |
7 |
> > > boot pool. That's the one GRUB loads. |
8 |
> > |
9 |
> > Sure, and in this case /boot is on my root pool. |
10 |
> > |
11 |
> > In any case, it would be nice if there was some way to tell what zpool |
12 |
> > features grub requires, as it is a limiting factor for whatever pool |
13 |
> > /boot happens to be on. |
14 |
> |
15 |
> Aren't new features only applied to newly created pools and datasets? If |
16 |
> /boot was compatible with GRUB it should still be. At least that's how I |
17 |
> read the einfo messages zfs spits out. |
18 |
|
19 |
That is correct. I want to know when I can enable the new features. |
20 |
Of course, it would also be nice to know which features must be |
21 |
disabled when creating a new boot pool. |
22 |
|
23 |
It is just frustrating that as far as I can tell, there is no |
24 |
documentation about what features grub supports. It wouldn't be hard |
25 |
for them to just say "here are the zpool features known to work in |
26 |
grub version foo." The best I've found is the Arch wiki, which has |
27 |
the disclaimer that it is probably out of date and to check the man |
28 |
pages, but of course the man pages don't actually say anything. |
29 |
|
30 |
-- |
31 |
Rich |