This information is outdated, your best bet is to follow the discussion on github as nobody is really sure at the moment.
Finding out exactly what got corrupted seems to be difficult/impossible. Active discussions:
https://github.com/openzfs/zfs/issues/15526
https://github.com/openzfs/zfs/issues/15554
All of this requires coreutils v9+
(not sure of the exact version), which you almost certainly have.
The second requirement is that you have either:
-
Run
zpool upgrade
after upgrading to2.2.0
, or manually enabledfeature@block_cloning
. -
Created a pool while on
2.2.0
as it was enabled by default.
You can check if the feature is enabled at all with something like:
zpool get all | grep block_cloning
If it's disabled, you are not affected by this.
If it's enabled, there seems to be a solution mentioned in the discussions linked above, but I haven't looked into it. If nothing works, temporarily downgrading coreutils
may be a solution.
A good rule of thumb is to avoid upgrading your pool or enabling features that you don't really need or want.
Enabling features is a one-way street, and it is not really possible to roll back.
Pinned Comments
kstolp commented on 2025-04-29 16:56 (UTC) (edited on 2025-05-03 09:40 (UTC) by kstolp)
OpenZFS currently supports Linux kernel versions 4.18 - 6.14, as declared in the META file.
Options if your Linux kernel's version is not within that range:
1) Switch to another Linux kernel, such as
linux-lts
.2) Prevent your kernel package from upgrading to an unsupported version until OpenZFS increases the maximum supported kernel version.
3) Modify this package to support your kernel by patching it on your local machine.
kstolp commented on 2023-09-29 00:34 (UTC)
When requesting changes, please include detailed reasoning for the change.
kstolp commented on 2023-01-07 09:31 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
You have two options:
1) Import the two keys into your keyring. ArchWiki article. You can find the key IDs in the PKGBUILD file, in the
validpgpkeys
array. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheck
argument tomakepkg
when building. (not recommended)