Package Details: zfs-dkms-git 2:2.1.99.r1271.g1c0c729ab4-1

Git Clone URL: (read-only, click to copy)
Package Base: zfs-dkms-git
Description: Kernel modules for the Zettabyte File System.
Upstream URL:
Keywords: illumos oracle solaris zol
Licenses: CDDL
Conflicts: spl-dkms, zfs-dkms
Provides: spl-dkms, SPL-MODULE, zfs-dkms, ZFS-MODULE
Replaces: spl-dkms-git
Submitter: isiachi
Maintainer: yurikoles
Last Packager: yurikoles
Votes: 24
Popularity: 0.000144
First Submitted: 2014-06-04 15:15 (UTC)
Last Updated: 2022-06-24 19:44 (UTC)

Required by (4)

Sources (2)

Latest Comments

epicaur commented on 2022-01-04 22:17 (UTC) (edited on 2022-01-05 07:48 (UTC) by epicaur)

This patch worked for me with the latest zfs-dkms-git (of course the header etc is not correct, I did not want to change that) - and the diff is created manually (editing files then running diff -u ..), not through git:

EDIT: converted to pastebin per AUR comment guidelines.

jungliztik commented on 2022-01-03 18:12 (UTC) (edited on 2022-01-03 18:13 (UTC) by jungliztik)

@eschwartz - do you have any thoughts/suggestions? I have just tried to install this package but got the same error that b0b reported a few weeks back. If it helps at all, the contents of the scripts/dkms.mkconf.rej are:

--- scripts/dkms.mkconf
+++ scripts/dkms.mkconf
@@ -63,7 +48,7 @@ POST_BUILD="scripts/dkms.postbuild
+MAKE[0]="make -C module/"
   [[ -r \${PACKAGE_CONFIG} ]] \\
   && source \${PACKAGE_CONFIG} \\

b0b commented on 2021-12-14 10:37 (UTC)

==> Starting prepare()...
patching file scripts/dkms.mkconf
Hunk #1 succeeded at 28 with fuzz 2 (offset 3 lines).
Hunk #2 FAILED at 63.
1 out of 2 hunks FAILED -- saving rejects to file scripts/dkms.mkconf.rej
==> ERROR: A failure occurred in prepare().

Kevdog commented on 2021-11-22 03:51 (UTC)

Just a heads up -- the option REMAKE_INITRD is now deprecated:

You may want to remove this option from the dkms.conf file within /usr/src/zfs-git

eschwartz commented on 2021-03-02 12:28 (UTC)

Oh shoot, I totally neglected to sync this change from the zfs-dkms package.

JohnyPea commented on 2021-03-02 10:23 (UTC) (edited on 2021-03-02 10:24 (UTC) by JohnyPea)

Hi the config problem can be solved by modyfying PKGBUILD:66
- cp config/config. config/missing config/sh "${dkmsdir}"/config/
+ cp config/compile config/config. config/missing config/sh "${dkmsdir}"/config/

esrevinu commented on 2021-01-19 09:26 (UTC)

Building DKMS module fails.

configure: error: cannot find required auxiliary files: compile

config/compile should be added into the package.

65a commented on 2020-12-06 08:05 (UTC)

I encountered an upstream bug at the current revision, wherein I could no longer mount encrypted datasets created under previous revisions. That issue is tracked here

Wanted to link this in case anyone else encounters this problem

65a commented on 2020-08-23 06:52 (UTC) (edited on 2020-08-23 06:55 (UTC) by 65a)

That's precisely what I did, and precisely when I encountered the dependency mismatch (perhaps yay's cache is causing the breakage).

Another thing I noticed is that the hooks provided by this package substantially differ from the old zfs-dkms-head-git. This definitely broke me coming from that package, since the hooks provided in this package have no support for loading keys.

Agreed that they should be separate packages, since one is kernel and the other is userland. There may be situations where only one or the other is needed (e.g. userland in a container).

eschwartz commented on 2020-08-23 02:16 (UTC)

When you update one, you should probably update the other at the same time. Just makepkg both of them and then pacman -U them together. No, nothing is "broken".

I'm not sure the dependency versioning should be lifted -- both packages build from the same repo and API updates to one might break if the other doesn't get updated together.

This might be less tricky to update the packages using makepkg -i if they were one single PKGBUILD with split packages, but then that would inconvenience people using packages which build the binary modules for one kernel, and only want zfs-utils-git.

65a commented on 2020-08-23 01:17 (UTC)

This package seems quite fragile with the version dependency on zfs-utils-git. Currently broken because of a mismatched version number != 1:0.8.0.r932.g317dbea17 when zfs-utils-git is compiled from AUR.

eschwartz commented on 2020-08-21 19:05 (UTC)

mindstormer, thanks for the report. I've deleted the -head package since it's a duplicate and breaks the rules of submission.

mindstormer commented on 2020-08-21 18:44 (UTC)

How does this compare to zfs-dkms-head-git? Which is recommended?

kerberizer commented on 2020-02-18 12:44 (UTC)


thieh commented on 2020-02-15 00:58 (UTC)

Hm....I got the following issue while trying to build the kernel module:

FATAL: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol '__rcu_read_lock'

kernel version is 5.5.3-arch1-1 / gcc 9.2.1 20200130

Anyone mind to enlighten me on this one?

JohnyPea commented on 2019-08-13 08:32 (UTC)

Hi, i was trying to use this package on linux53 with errors and found a discussion where the problem was identified: I have used the suggestion and with this patch: and PKGBUILD update: it builds and works. Tested on Manjaro 5.2.8 and 5.3-rc4 kernels.

javashin commented on 2019-07-08 20:58 (UTC)

this pkg install old zfs zpool --version zfs-0.8.0-116_g1086f5421 zfs-kmod-0.8.0-1

eschwartz commented on 2018-12-02 05:16 (UTC) (edited on 2018-12-02 05:29 (UTC) by eschwartz)

Hmm, using the date of the latest commit is at least sort of reasonable once you know where it actually comes from. (Nevertheless, I personally consider dates to be inelegant, and they introduce potential inconsistencies given that git does not enforce monotonically increasing dates, and depending how you format it, timezone differences can cause it to decrease anyway.)

That being said, and while this is obviously somewhat subjective, I'm not sure I see the reasoning anyway -- it's a git package being run from git master, why would the existence of maintenance releases on some other branch matter?

minextu commented on 2018-12-01 13:47 (UTC)

@eschwartz The reason behind having the latest commit date as the version can be found here:

The git version pinning was added here: But I agree, I should be re-added. This will require some work on the archzfs buildscripts. I will look into that when I have some more spare time

eschwartz commented on 2018-11-28 17:18 (UTC) (edited on 2018-11-28 17:33 (UTC) by eschwartz)

Hi, please immediately revert the pinning of commit hashes as this is a git package and git packages manifestly do not use pinned commits (because if they did use pinned commits, then they would be a duplicate of the non-git package). Please fix any other packages you maintain as well.

This also means you can stop committing frivolous updates to the pkgver of a git package.

Also please re-add the pkgver() function you removed, restore the package to using the actual version as opposed to some terrible date chosen out of a hat, and add an epoch variable to ensure users can actually migrate back to the original pkgver format. I'm not sure I understand the logic of using an unreliable date (chosen using an unknown manual algorithm) instead of proper revision numbers, and it's certainly impossible to know when the commit logs don't mention any reason at all.

itoffshore commented on 2018-10-13 12:44 (UTC)

@nemster - in /etc/makepkg.conf see MAKEFLAGS

using -j6 takes around 10 minutes on AMD FX to build the modules per kernel

nemster commented on 2018-10-05 16:58 (UTC)

compiling is always slow, anyone knows how to add makeflags?

karl_gerh commented on 2018-04-23 05:28 (UTC)

Beware, this package doesn't work with kernel 4.16.3. You'll have to downgrade your kernel to use ZFS again.

pnmice commented on 2017-12-23 04:14 (UTC)

mkinitcpio -p linux

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img ==> Starting build: 4.14.8-1-ARCH ... -> Running build hook: [zfs] ==> ERROR: module not found: zpios' ==> ERROR: file not found:zpios'

pacman -Q | grep -e zfs -e spl

spl-dkms-git 0.7.0_r22_gc9821f1-1 spl-utils-dkms-git 0.7.0_r22_gc9821f1-1 zfs-dkms-git 0.7.0_r225_g823d48bfb-1 zfs-utils-dkms-git 0.7.0_r225_g823d48bfb-1

swordfeng commented on 2017-12-22 05:05 (UTC) (edited on 2017-12-22 05:05 (UTC) by swordfeng)

I guess the systemd files are not installed after a certain version...

abrilevskiy commented on 2017-12-21 07:11 (UTC) is not enabled in systemd after installation

-> Running build hook: [zfs] ==> ERROR: module not found: zpios' ==> ERROR: file not found:zpios'

patrickh commented on 2017-11-10 14:57 (UTC)

> Please add zfs encryption support to the initcpio hook yes, that would be fantastic!

minextu commented on 2017-09-08 17:30 (UTC)

Please add zfs encryption support to the initcpio hook (see zfs_decrypt_fs() in

sylveon commented on 2017-07-28 15:20 (UTC) (edited on 2017-07-28 15:34 (UTC) by sylveon)

Right now if you install it pacaur will constantly try to update it, because apparently rc3 is a bigger version number than r0: :: spl-dkms-git: ignoring package upgrade (0.7.0_r0_g1f2671b-1 => latest) :: spl-utils-dkms-git: ignoring package upgrade (0.7.0_r0_g1f2671b-1 => latest) :: zfs-dkms-git: ignoring package upgrade (0.7.0_r0_gccad64314-1 => latest) :: zfs-utils-dkms-git: ignoring package upgrade (0.7.0_r0_gccad64314-1 => latest) Also please remove zlib_deflate from the initcpio hook while you're at it. Will remove the following error when running mkinitcpio: ==> ERROR: module not found: `zlib_deflate' ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img ==> WARNING: errors were encountered during the build. The image may not be complete.

skjeggape commented on 2017-07-04 20:55 (UTC)

whoops, should not be here, consernes the zfs/dkms package. sorry

skjeggape commented on 2017-07-04 20:40 (UTC)

After latest update my system wont boot, normal recover procedure wont solve the issue. at boot i get following error: This pool uses the following feature(s) not supported by this system: org.zfsonlinux:userobj_accounting (User/Group object accounting.) All unsupported features are only required for writing to the pool. The pool can be imported using '-o readonly=on'. cannot import 'poolname' error failed to mount real root etc etc.

Marcel_K commented on 2017-06-27 03:37 (UTC)

That's an issue with ArchZFS, this package is not to blame. BTW, why is this package flagged out-of-date?

abrilevskiy commented on 2017-06-26 10:56 (UTC)

==> ERROR: module not found: `zlib_deflate' ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img ==> WARNING: errors were encountered during the build. The image may not be complete. error: command failed to execute correctly

Marcel_K commented on 2017-02-23 00:57 (UTC)

On a second thought, rebuild only fails when doing a regular `pacman -Syu`. It appears there is a BUILD_DEPENDS[0]="spl" line in dkms.conf, so dkms should build these modules in the correct order. However, the pacman hook doesn't take this option into account, resulting in failures. There is a bug report about this issue:

Marcel_K commented on 2017-02-01 18:57 (UTC)

You have to be sure spl is compiled *before* zfs is. Sometimes it will be, sometimes not. @isiachi: Is there a way to give spl compilation precedence over zfs? I can't find a method. The only way to be sure is reinstall spl from AUR manually, then reinstall zfs.

Atraii commented on 2017-02-01 18:21 (UTC)

I'm not getting this to work with the latest kernel either. I can't modprobe it, `sudo modprobe zfs` results in: modprobe: FATAL: Module zfs not found in directory /lib/modules/4.9.6-1-ARCH I attempted to reinstall it with dkms, getting this error with `dkms autoinstall`: ...cut... checking spl source directory... /usr/src/spl-0.7.0 checking spl build directory... /var/lib/dkms/spl/0.7.0/4.9.6-1-ARCH/x86_64 configure: error: *** Please make sure the kmod spl devel <kernel> package for your *** distribution is installed then try again. If that fails you *** can specify the location of the spl objects with the *** '--with-spl-obj=PATH' option. Failed to find spl_config.h in *** any of the following: /usr/src/spl-0.7.0/4.9.6-1-ARCH /usr/src/spl-0.7.

Marcel_K commented on 2017-02-01 17:46 (UTC)

Please be more verbose: what does not work? I am using linux-zen aside from stock Arch linux package, and for both kernels dkms modules are build and installed correctly (running linux-zen 4.9.6 right now).

tritron commented on 2017-02-01 16:02 (UTC)

This package does not work with latest kernel

WoefulDerelict commented on 2016-10-20 19:48 (UTC)

I'm not sure the package is to blame. As of the most recent commit this afternoon this builds and works on my system with a root zfs pool. The only issue I'm currently experiencing is tied to and effects the dkms install. It is described here

sinetek commented on 2016-10-20 02:47 (UTC)

Beware! This package killed my / installation, as the rootfs fails to mount during boot. It whines about canonicalization error 2. No idea what this means.

OrdinaryMagician commented on 2016-09-12 17:34 (UTC) (edited on 2016-09-12 17:35 (UTC) by OrdinaryMagician)

The initcpio hook and install files are outdated, they don't even have any of the fixes from the archzfs ones. This breaks booting right now because of the missing

WoefulDerelict commented on 2016-06-14 18:25 (UTC)

There have been recent changes to the ZoL codebase that are noteworthy as they may cause issues during update. The configuration files for systemd have changed and the new services are not enabled by default after updating. As the package lacks the preset data it is necessary to enable the services manually for zfs filesystems to mount properly.

BugMaze commented on 2016-04-23 17:53 (UTC)

This package fails at the dkms step , the solution suggested by ajs124 below works perfectly . Thanks .

commented on 2016-04-23 12:23 (UTC)

This package, as well as spl-dkms-git, is broken. They both fail to compile, because dkms expects a Makefile, which the PKGBUILD generates with and configure, but does not include in the package, because it uses git archive. Simply replacing the "git archive | tar" part with "cp -r . ${dkmsdir}/" fixes this problem.

isiachi commented on 2015-12-29 15:58 (UTC)

Git branch. You can find stable here:

WoefulDerelict commented on 2015-10-03 05:52 (UTC)

bjin suggested that this package should be reworked to build from the git master branch and maintained. As I happen to agree with this idea I've generated the necessary resources. Users can edit the _branch variable should they wish to build another branch than master providing added versatility. The resources can be found at the following URLs:

isiachi commented on 2015-08-31 12:03 (UTC)

New package: