aboutsummaryrefslogtreecommitdiffstats
path: root/man
diff options
context:
space:
mode:
authorRichard Laager <[email protected]>2020-08-18 01:12:39 -0500
committerGitHub <[email protected]>2020-08-17 23:12:39 -0700
commiteaa25f1a8e5f6ed72c2095a06df14621ed04ee6d (patch)
treec7dc274d9cfbaee1aea9a22ac2c153f8400b9c2a /man
parentd60c0dbdf390c4fe7ad66bc2f79ee076bb046fb1 (diff)
Remove GRUB restrictions
The GRUB restrictions are based around the pool's bootfs property. Given the current situation where GRUB is not staying current with OpenZFS pool features, having either a non-ZFS /boot or a separate pool with limited features are pretty much the only long-term answers for GRUB support. Only the second case matters in this context. For the restrictions to be useful, the bootfs property would have to be set on the boot pool, because that is where we need the restrictions, as that is the pool that GRUB reads from. The documentation for bootfs describes it as pointing to the root pool. That's also how it's used in the initramfs. ZFS does not allow setting bootfs to point to a dataset in another pool. (If it did, it'd be difficult-to-impossible to enforce these restrictions cross-pool). Accordingly, bootfs is pretty much useless for GRUB scenarios moving forward. Even for users who have only one pool, the existing restrictions for GRUB are incomplete. They don't prevent you from enabling the unsupported checksums, for example. For that reason, I have ripped out all the GRUB restrictions. A little longer-term, I think extending the proposed features=portable system to define a features=grub is a much more useful approach. The user could set that on the boot pool at creation, and things would Just Work. Reviewed-by: Paul Dagnelie <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Richard Laager <[email protected]> Closes #8627
Diffstat (limited to 'man')
-rw-r--r--man/man5/zpool-features.59
-rw-r--r--man/man8/zfsprops.82
2 files changed, 0 insertions, 11 deletions
diff --git a/man/man5/zpool-features.5 b/man/man5/zpool-features.5
index 3f690c334..0416afaa3 100644
--- a/man/man5/zpool-features.5
+++ b/man/man5/zpool-features.5
@@ -340,9 +340,6 @@ can turn on the \fBedonr\fR checksum on any dataset using the
and will return to being \fBenabled\fR once all filesystems that have
ever had their checksum set to \fBedonr\fR are destroyed.
-The \fBedonr\fR feature is not supported by GRUB and must not be used on
-the pool if GRUB needs to access the pool (e.g. for /boot).
-
FreeBSD does not support the \fBedonr\fR feature.
.RE
@@ -827,9 +824,6 @@ can turn on the \fBsha512\fR checksum on any dataset using
\fBactive\fR once a \fBchecksum\fR property has been set to \fBsha512\fR,
and will return to being \fBenabled\fR once all filesystems that have
ever had their checksum set to \fBsha512\fR are destroyed.
-
-The \fBsha512\fR feature is not supported by GRUB and must not be used on
-the pool if GRUB needs to access the pool (e.g. for /boot).
.RE
.sp
@@ -861,9 +855,6 @@ can turn on the \fBskein\fR checksum on any dataset using
\fBactive\fR once a \fBchecksum\fR property has been set to \fBskein\fR,
and will return to being \fBenabled\fR once all filesystems that have
ever had their checksum set to \fBskein\fR are destroyed.
-
-The \fBskein\fR feature is not supported by GRUB and must not be used on
-the pool if GRUB needs to access the pool (e.g. for /boot).
.RE
.sp
diff --git a/man/man8/zfsprops.8 b/man/man8/zfsprops.8
index 5a2b45e64..1fcb07c6f 100644
--- a/man/man8/zfsprops.8
+++ b/man/man8/zfsprops.8
@@ -762,8 +762,6 @@ The
and
.Sy edonr
checksum algorithms require enabling the appropriate features on the pool.
-These pool features are not supported by GRUB and must not be used on the
-pool if GRUB needs to access the pool (e.g. for /boot).
FreeBSD does not support the
.Sy edonr
algorithm.