If you're reckless like me and updated without reading the notes informing that zfs is broken on 6.5 just install linux-lts and linux-lts-headers for the time being, dont forget to update your bootloader to boot into linux-lts.
Search Criteria
Package Details: zfs-dkms 2.2.4-2
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: | 162 |
Popularity: | 1.89 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2024-05-20 09:56 (UTC) |
Dependencies (2)
- dkms
- zfs-utilsAUR (zfs-linux-gitAUR, zfs-utils-gitAUR, zfs-utils-staging-gitAUR)
Required by (19)
- 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)
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 59 Next › Last »
h0m3 commented on 2023-09-13 02:03 (UTC) (edited on 2023-09-13 02:04 (UTC) by h0m3)
notjas commented on 2023-09-12 23:08 (UTC)
Stay on 6.4.12 for time being, do not take linux or linux-headers until this package is updated to support 6.5
truncs commented on 2023-09-10 21:50 (UTC)
Linux 6.5 version errors out while building the dkms
==> dkms install --no-depmod zfs/2.1.12 -k 6.5.2-arch1-1
^[[24~configure: error:
*** None of the expected "bops->release()" interfaces were detected.
*** This may be because your kernel version is newer than what is
*** supported, or you are using a patched custom kernel with
*** incompatible modifications.
***
*** ZFS Version: zfs-2.1.12-1
*** Compatible Kernels: 3.10 - 6.3
Lenry commented on 2023-09-08 14:05 (UTC)
the current version is not compatible with Linux kernel v6.5, so if you using that, don't upgrade
fryfrog commented on 2023-06-07 21:44 (UTC)
@sgh: You need to build both and then install both at the same time. There's an option for this in paur
, there is probably one for pacaur
too.
sgh commented on 2023-06-07 21:19 (UTC)
pacaur -S zfs-dkms fails and gives me this. It seems like zfs-dkms and zfs-utils are not in sync.
==> Finished making: zfs-utils 2.1.12-1 (Wed Jun 7 23:13:31 2023) ==> Cleaning up... :: Installing zfs-utils package(s)... loading packages... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing zfs-utils (2.1.12-1) breaks dependency 'zfs-utils=2.1.11' required by zfs-dkms :: Building zfs-dkms package(s)... ==> Making package: zfs-dkms 2.1.12-1 (Wed Jun 7 23:13:32 2023)
meithan commented on 2023-06-07 02:35 (UTC)
ZFS 2.1.12, which adds official support for the Linux 6.3 kernel, has been released!
karns commented on 2023-06-03 20:03 (UTC)
@meithan: would introducing a separate package be a possible solution? Something like zfs-dkms-stable
which would be identical with the exception of having a kernel version gate in the conflicts.
For now I am just using linux-lts.
meithan commented on 2023-06-03 04:58 (UTC)
@sphere101 They have successfully patched 6.3 support upstream, but those patches haven't been backported to the next stable release yet. There's no indication about when that will be completed. Everyone should stick to kernel 6.2 or previous for the time being.
meithan commented on 2023-06-03 04:51 (UTC)
@mabod Using zfs-dkms
is a personal choice we make consciously in order to be able to stay on the bleeding edge. We understand and accept the risks that implies. That said, it doesn't mean we shouldn't explore ways to reduce those risks, if it's viable. That's all were doing. If there's no way, we'll live with that.
Pinned Comments
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
validpgpkeys
array. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheck
argument tomakepkg
when building. (not recommended)