Arch Linux User Repository

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)

@jalley: support for kernel 6.7 is in git master and 2.2.3-staging branch, but not in zfs 2.2.2. zfs 2.2.3 is not yet released. If you need support for kernel 6.7 you can use the staging packages: zfs-dkms-staging-git and zfs-utils-staging-git

The OpenZFS meta file says it now supports the 6.7 kernel, but it looks like they pined it to version 2.2.99 which was previously released in July. I don't understand but was hoping someone smarter than me would take a look.

@bjin - Thank you for your much appreciated zfs-dkms-staging-git effort! My hand was 'forced' when my go to kernel, linux-hardened, got bumped to 6.7.2 today (28 Jan). zfs-dkms-staging-git built and installed correctly against linux, -zen and -hardened.

Cheers!!

Hi, I've been using zfs-dkms for a while with the lts kernel, and have just noticed that upon upgrade of kernel many of the older kernel zfs build artifacts are remaining on the filesystem in /usr/lib/modules/ Looks like the artifacts are in
/usr/lib/modules/6.1.70-1-lts/build/module/zfs/.deps/
and
/usr/lib/modules/6.1.70-1-lts/build/tests/zfs-tests
See https://bbs.archlinux.org/viewtopic.php?id=291992
e.g.
drwxr-xr-x 3 root root 4.0K Oct 29 18:42 6.1.58-1-lts
drwxr-xr-x 3 root root 4.0K Nov 5 09:57 6.1.60-1-lts
drwxr-xr-x 3 root root 4.0K Nov 11 09:31 6.1.61-1-lts
drwxr-xr-x 3 root root 4.0K Nov 24 08:00 6.1.62-1-lts
drwxr-xr-x 3 root root 4.0K Dec 12 17:54 6.1.63-1-lts
drwxr-xr-x 3 root root 4.0K Dec 23 15:49 6.1.67-1-lts
drwxr-xr-x 3 root root 4.0K Jan 5 09:29 6.1.69-1-lts
drwxr-xr-x 5 root root 4.0K Jan 19 20:19 6.1.70-1-lts

Anyone else notice similar?

I made a new AUR package called zfs-dkms-staging-git1. It has all the patches needed to make zfs-dkms work with the new 6.7 kernel. This package currently tracks the zfs-2.2.3-staging branch from the upstream, including all the staging changes to the stable 2.2.x branch. It's more stable than "zfs-dkms-git" but slightly less stable than "zfs-dkms" which tracks release tags.

If you're eager to use the new 6.7 kernel like me, you can install this package before v2.2.3 is officially tagged. Once v2.2.3 is out, you can switch back to the 'zfs-dkms' package.

I relaxed the dependencies on the zfs-util package to make switching between these two packages easier and less troublesome.

IMO you can publish patches or a modified kernel as long as you comply with the GPL-2.0 license, under which the Linux kernel and specifically the mentioned header file is published. On ZFS side, the CDDL license appears clear enough for LLNL (military) to stay involved, and Ubuntu or ProxMox to ship binaries. As far as I know no company employing OpenZFS has been sued or blackmailed by Oracle. Worst thing to happen if your fixes gain traction in a sizable community is getting punched in the face by gregkh at a conference and Linus won't invite you to the hot tub after show event. Your changes will also never be upstreamed.

@bsdice I confirm that your suggestion for include/linux/export.h L87,L89 emptying the GPL string allows dkms to build the zfs module, and it seems to load and work with 6.6.10. I also tried the amd64 version which works without modification. I noticed that the 6.1 kernel source for aarch64 had the sting nulled. Not sure if it poses a problem that such a patch is distributed?

The problem with linux-lts (edit: ment 6.1.x branch) is the continuous breakage due to incomplete or wrong backports. I no longer trust it. It sounds funny and wrong but if you want stable, use Torvald's point releases. Second best imho is to use the n-1 kernel with moderate backporting. Right now that is 6.6.10. Of course you'd have to develop a strategy so kernels no longer roll during updates. Which you should do anyways when using ZFS.

Note that linux-lts was bumped to 6.6 a day or so ago.

I recommend to use linux-lts kernel instead of stock linux or linux-zen. I'm using linux-lts and no more problems with incompatible kernel :-)