I have installed spl-dkms & zfs-dkms 0.7.5 with the latest kernel 4.14.10-1 but for some reason the zfs kernel modules are not loading during boot. If I run '/sbin/modprobe zfs' then the modules load and I can mount the zpool. Anybody else had this issue?
Search Criteria
Package Details: zfs-dkms 2.3.2-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/zfs-dkms.git (read-only, click to copy) |
|---|---|
| Package Base: | zfs-dkms |
| Description: | Kernel modules for the Zettabyte File System. |
| Upstream URL: | https://zfsonlinux.org/ |
| Licenses: | CDDL |
| Provides: | SPL-MODULE, zfs, ZFS-MODULE |
| Submitter: | isiachi |
| Maintainer: | kstolp |
| Last Packager: | kstolp |
| Votes: | 188 |
| Popularity: | 2.27 |
| First Submitted: | 2015-08-31 12:01 (UTC) |
| Last Updated: | 2025-05-03 09:40 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR)
- zfs-utilsAUR (zfs-utils-gitAUR, zfs-linux-gitAUR, zfs-utils-staging-gitAUR)
Required by (20)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfs-openrc
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (3)
jjb2016 commented on 2018-01-02 11:15 (UTC)
lilydjwg commented on 2017-12-22 00:29 (UTC)
They are available in the archlinuxcn repo too (scroll one page up).
misanthropist commented on 2017-12-21 16:50 (UTC)
@bus I noticed that zfs-dkms and spl-dkms are available as pre-built packages in the archzfs repo. https://wiki.archlinux.org/index.php/Unofficial_user_repositories#archzfs
mrueg commented on 2017-12-14 23:24 (UTC)
Simply replacing "0.7.3" with "0.7.4" in the PKGBUILD seems to work for me. (When used with zfs-dkms, I did the same there and uninstalled both packages prior to reinstalling the newer versions.)
codyps commented on 2017-12-04 21:17 (UTC) (edited on 2017-12-04 21:17 (UTC) by codyps)
broken with linux 4.14
upstream issue: https://github.com/zfsonlinux/spl/issues/656, https://github.com/zfsonlinux/spl/pull/659
jcstryker commented on 2017-11-28 18:46 (UTC)
Would it be a good idea to have this package support the zfs-utils-common package along with spl-utils-common?
sylveon commented on 2017-11-06 02:37 (UTC)
No, a stable release has not made it with encryption yet. You're probably searching for zfs-dkms-git if you want encryption.
francoism90 commented on 2017-11-05 19:13 (UTC) (edited on 2017-11-05 19:13 (UTC) by francoism90)
I'm a bit confused should this release not include encryption?
zhangyoufu commented on 2017-08-21 10:03 (UTC) (edited on 2017-08-21 10:04 (UTC) by zhangyoufu)
zfs datasets mounted by zfs.initcpio.hook got incorrect options.
The line related: mount -t zfs -o "zfsutil,${rwopt_exp}" "${dataset}" "${node}${mountpoint}"
Calling mount manually ignores several options set on the zfs dataset.
For example, I set zfs option atime=no on my rootfs and the result is relatime enabled. (showing as temporary in zfs get)
I made a small utility(~11K binary) doing what zfs mount does and put it inside initramfs.
See https://github.com/zhangyoufu/zfs_mount
I changed `mount -t zfs -o` to my `zfs_mount` and get this problem fixed.
A better solution would be providing something similar to altroot for zfs mount command, which requires upstream changes.
Pinned Comments
kstolp commented on 2025-04-29 16:56 (UTC) (edited on 2025-05-03 09:40 (UTC) by kstolp)
OpenZFS currently supports Linux kernel versions 4.18 - 6.14, 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.
kstolp commented on 2023-09-29 00:34 (UTC)
When requesting changes, please include detailed reasoning for the change.
kstolp commented on 2023-01-07 09:31 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
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
validpgpkeysarray. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheckargument tomakepkgwhen building. (not recommended)