Package Details: zfs-dkms

Git Clone URL: (read-only)
Package Base: zfs-dkms
Description: Kernel modules for the Zettabyte File System.
Upstream URL:
Licenses: CDDL
Conflicts: zfs-git, zfs-lts
Provides: zfs
Submitter: isiachi
Maintainer: isiachi
Last Packager: isiachi
Votes: 21
Popularity: 1.143900
First Submitted: 2015-08-31 12:01
Last Updated: 2016-09-20 20:44

Required by (5)

Sources (4)

Latest Comments

ShaunPC commented on 2016-12-19 15:50

@salvert I too have been having trouble with dkms installing the modules in the wrong order. There does not seem to be an order implemented by the zfs module. On investigation it appears that dkms already has a module dependency check implemented. So my guess is that the zfs module is not using the dkms dependency check correctly. I've been rerunning the dkms install for zfs manually after my updates and then rerunning mkinitcpio to regenerate my kernel images. That has worked for me till this problem gets fixed.

saivert commented on 2016-12-14 13:50

On a recent upgrade to linux 4.8.13-1, the hook for building DKMS modules somehow tried to build zfs before spl and zfs depends on spl..

:: Running post-transaction hooks...
( 1/10) Install DKMS modules
==> dkms install zfs/ -k 4.8.13-1-ARCH
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.
Error! Bad return status for module build on kernel: 4.8.13-1-ARCH (x86_64)
Consult /var/lib/dkms/zfs/ for more information.
==> dkms install spl/ -k 4.8.13-1-ARCH
( 2/10) Updating linux initcpios

Is there a way to specify ordering of DKMS modules when building them or is this a problem with this package?

brando56894 commented on 2016-12-13 01:17

You should change the shebang to /usr/bin/python2, when it gets to the L2 summary it crashes for me using python 3.x

lilydjwg commented on 2016-11-04 12:28

You left out a "&" here:

seschwar commented on 2016-10-23 19:31

You can find fixes for my complaints at

There's also support for GRUB's root=ZFS=mypool/myfs kernel command line syntax.

seschwar commented on 2016-09-22 21:34


You updated the initcpio hook to mount all child data sets of the dataset mounted on /. See line 59 in /usr/lib/initcpio/hooks/zfs.

This is quite problematic since the script completely ignores the canmount property. Therefore datasets with canmount=off and canmount=noauto get mounted as well. This completely breaks the semantics of these properties.

The manual page of the zfs command has the following sentence in it:

> Setting this property [canmount] to off allows datasets to be used solely as a mechanism to inherit properties.

I had a dataset for /var with canmount=off for exactly this purpose. Imagine my surprise when this empty dataset got mounted leaving me with an almost empty /var. Quite the breaking change you introduced there.

I'm not quite sure about the motivation behind this. It could be useful for boot environments. Something similar was discussed recently on a FreeBSD mailing list: However they should be careful when repurposing an established setting of property. Changing how the mounting of datasets work would break backwards compatibility.

isiachi commented on 2016-09-20 19:45

| Upgrading this package from the previous version does not work, you have to remove it and readd to your system.
| The issue is some kind of dependency circle between this package and the spl-dkms:

This is because you have to build all the packages on your own and install all of them together.

Otherwise you have to install the spl packages with the -d option.

# pacman -Ud spl-dkms### spl-utils###

This is a AUR helper problem. It's not my fault. Stop saying things that have no sense and learn how to use pacman.

isiachi commented on 2016-09-20 19:36


We are talking of a filesystem and this is a stable branch. I've already said that I wasn't going to add a single commit from the master branch, too much things were changed.

Unfortunately I wasn't able to lock the package to a specific kernel version because the kernel is not a dependecy.

And also take a breath and calm down.

RubenKelevra commented on 2016-09-20 19:34

@utsi just use a conflict constraint for such cases:

conflict linux>4.6.xx etc. :)

RubenKelevra commented on 2016-09-20 19:31

Upgrading this package from the previous version does not work, you have to remove it and readd to your system.

The issue is some kind of dependency circle between this package and the spl-dkms:

Sorry that it is in german:

Fehler: Konnte den Vorgang nicht vorbereiten (Kann Abhängigkeiten nicht erfüllen)
:: zfs-dkms: das Installieren von spl-dkms ( löscht ein benötigtes Packet von 'spl-dkms='

All comments