Package Details: zfs-dkms 2.1.0-1

Git Clone URL: (read-only, click to copy)
Package Base: zfs-dkms
Description: Kernel modules for the Zettabyte File System.
Upstream URL:
Licenses: CDDL
Conflicts: spl-dkms
Provides: SPL-MODULE=2.1.0, ZFS-MODULE=2.1.0, spl-dkms, zfs
Replaces: spl-dkms
Submitter: isiachi
Maintainer: eschwartz
Last Packager: eschwartz
Votes: 117
Popularity: 3.26
First Submitted: 2015-08-31 12:01
Last Updated: 2021-07-02 21:31

Required by (18)

Sources (3)

Pinned Comments

eschwartz commented on 2020-03-22 16:01


Doesn't appear to build, at least on my system.

==> Verifying source file signatures with gpg...
zfs-0.8.3.tar.gz ... FAILED (unknown public key 6AD860EED4598027)
==> ERROR: One or more PGP signatures could not be verified!


This package doesn't support people who have failed to read the wiki page, or cannot interpret error messages.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

thedanbob commented on 2021-02-07 20:10

Now that autoconf 2.71 and glibc 2.33 are out of testing this should install normally.

Ranguvar commented on 2021-02-06 02:05

greencopper, see the comments below. I don't think you're on [testing] as you may need to be.

greencopper commented on 2021-02-06 01:36

==> Starting prepare()...
patching file scripts/dkms.mkconf
Hunk #1 succeeded at 26 with fuzz 2 (offset 1 line).
Hunk #2 succeeded at 60 with fuzz 1 (offset -3 lines). error: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION or AM_GNU_GETTEXT_REQUIRE_VERSION
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'.
libtoolize: copying file 'config/libtool.m4'
libtoolize: copying file 'config/ltoptions.m4'
libtoolize: copying file 'config/ltsugar.m4'
libtoolize: copying file 'config/ltversion.m4'
libtoolize: copying file 'config/lt~obsolete.m4' installing 'config/compile' installing 'config/missing'
==> ERROR: A failure occurred in prepare().

Zepman commented on 2021-02-05 07:32

Manually updating the package to version 2.0.2 works if this patch is added. It is a workaround for an autoconf issue that will be fixed in a new version, which is not available yet.

After installation, I had to manually copy config/compile from the sources to /usr/src/zfs-2.0.2/config/. A one-time manual recompilation of the DKMS module allowed me to build the module for my new kernel. I used:

dkms install -m zfs -v 2.0.2 -k 5.4.94-1-lts

Probably these steps can be integrated in PKGBUILD.

Ranguvar commented on 2021-02-03 04:59

autoconf 2.71 packaged in testing.

Tried building 2.0.2 and made the package but couldn't get DKMS to compile. Could be on my end. Package might need tweaking.

Seems to not generate the Makefile. I'm bad at finding the relevant logs (past make.log from DKMS).

eschwartz commented on 2021-01-29 00:07

I pinged the autoconf maintainer on the 25th. He was busy, but 2.71 got released today. Waiting for it to get packaged, then I'll test updating this package.

gammy commented on 2021-01-25 13:25

+1 on the upstream autoconf issue. I also noticed that dkms-install recompiles the whole shebang in the post-transaction hooks (i.e Install DKMS modules stage) even though all of the modules were already built. On "slower" systems (1.8GHz Atom CPUs for example) with multiple kernels, this adds several extra hours for the installation as it essentially doubles the work for no reason. There is no commandline output during this time. Further, said hooks expect dpkg-architecture to be installed, which is usually not the case on non-debian systems.

storm.continuity commented on 2021-01-19 08:48

@iusrlinearb thank you for reassuring me mate. I have updates my systems today and besides that "warning" it works like a charm :)

iusrlinearb commented on 2021-01-13 16:20

Thanks for keeping on top of it, my 2 systems appreciate it!

eschwartz commented on 2021-01-13 16:08

The update doesn't fix the autoconf 2.70 error. It does fix a separate issue, which are some additional autoconf 2.70 warnings.

There was supposed to be a new autoconf 2.70.1 / 2.71 release "later this week", but that was last week, so maybe the autoconf maintainer didn't have time either. ;)