Arch Linux User Repository

OpenZFS currently supports Linux kernel versions 4.18 - 6.13, 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.

When requesting changes, please include detailed reasoning for the change.

If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.

==> ERROR: One or more PGP signatures could not be verified!

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 to makepkg when building. (not recommended)

Hey @kstolp, when you update to 2.3.2 it'd be awesome if you could bump back down pkgrel to 1 on this and zfs-utils! :)

Anyone else having problems with linux-lts-6.12.25-2?

==> dkms install --no-depmod zfs/2.3.1 -k 6.12.25-2-lts
Deprecated feature: CLEAN (/usr/src/zfs-2.3.1/dkms.conf)
==> WARNING: `dkms install --no-depmod zfs/2.3.1 -k 6.12.25-2-lts' exited 1

If I try to manually build with dkms install --no-depmod zfs/2.3.1 -k 6.12.25-2-lts

checking kernel source version... 6.12.25-2-lts
checking for kernel config option compatibility... done
checking whether CONFIG_MODULES is defined... no
configure: error: 
        *** This kernel does not include the required loadable module
        *** support!
        ***
        *** To build OpenZFS as a loadable Linux kernel module
        *** enable loadable module support by setting
        *** `CONFIG_MODULES=y` in the kernel configuration and run
        *** `make modules_prepare` in the Linux source tree.
        ***
        *** If you don't intend to enable loadable kernel module
        *** support, please compile OpenZFS as a Linux kernel built-in.
        ***
        *** Prepare the Linux source tree by running `make prepare`,
        *** use the OpenZFS `--enable-linux-builtin` configure option,
        *** copy the OpenZFS sources into the Linux source tree using
        *** `./copy-builtin <linux source directory>`,
        *** set `CONFIG_ZFS=y` in the kernel configuration and compile
        *** kernel as usual.

OpenZFS currently supports Linux kernel versions 4.18 - 6.13, 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.

@mabod thank you! Exactly what I needed 😃

@notjas: Why dont you just edit the META file to contain "Linux-Maximum: 6.99"

The patch is this one: https://github.com/openzfs/zfs/pull/15986/

Also, there is a new config option to disable that behaviour:

--enable-linux-experimental Allow building against some unsupported kernel

Hi 👋 I'm trying to find how to override the kernel version check, all I remember when it was merged a few months back is a ridiculously long name, intended to make the user read/pay attention. a) I'm having no luck finding that command/switch via google, and I need it for my system b) can I just undo that fucking patch completely which implemented this shit, never have I ever broken my install this way, but that damn patch continues to fuck me repeatedly. Why are we okay being treated as if this were macOS or Windows and we need our hands held...I issue a command I expect it to be executed, any subsequent potential issues are my responsibility... I just want the check gone, permanently if at all possible. The fact that it fails, and then doesn't even fucking tell you how to override... 🫤

@mabod: Modifying the META file or the dkms.conf file both involve editing the packages file, which doesn't feel great. In addition, if there was an update to the package the modification would not survive and a new kernel would install and the zfs module would not be built.

@yurikoles: It can still be an intended behavior and require research, but the package itself could make it smarter and safer while still maintaining the need for understanding.

I wish I had a good idea of how to do that, I'd suggest it. The package obviously shouldn't just use the option / modify the META file itself. But it would be nice if there was a route that didn't leave you vulnerable to a zfs-dkms package update making it not build.

For anyone doing research, no changes beyond updating the META are required for 6.13.

@fryfrog it's an intended behaviour, people need to do some research before waste their data on ZFS pools and complain about this fact on the upstream GitHub.

@fryfrog: Why would you want to do that? To compile the zfs module for kernel 6.13 you could just edit the META file and set "Linux-Maximum: 6.13".

Is there a smart way to add --enable-linux-experimental to /usr/src/zfs-$pkgver/dkms.conf? Or maybe is there a smart way this package could make it... maybe not easier, but more discoverable?