Honestly I just use the arch-zfs repo. They provide prebuilt binaries for all the kernels available in the official Arch repos (so less headaches and time wasted compiling) as well as DKMS versions and are fast at updating their builds to new kernel or ZFS versions as well as applying patches to make them buildable for newer kernel/compiler versions.
Search Criteria
Package Details: zfs-dkms 2.3.1-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: | 186 |
Popularity: | 1.52 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2025-03-11 07:23 (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)
Latest Comments
« First ‹ Previous 1 .. 45 46 47 48 49 50 51 52 53 54 55 .. 64 Next › Last »
sylveon commented on 2018-10-21 16:21 (UTC)
allspark commented on 2018-10-20 09:09 (UTC)
i'm using zfs with version 0.7.11 without problems
from https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.10 Updated 9/17/18: We've found a serious regression in 0.7.10 (#7906 #7899). Please use 0.7.9 or 0.7.11.
so 0.7.11 should be ok
RubenKelevra commented on 2018-10-18 03:23 (UTC)
@bus yeah, I sent a orphan request again. I got some spare time to maintain this package in time. I don't see why he should keep this package if he has no spare time.
hzhangxyz commented on 2018-10-15 14:40 (UTC)
in this package /etc/sudoers.d/ permission is 755 but in system it is 750
lilydjwg commented on 2018-10-12 07:44 (UTC)
@karcher it actually works. In this way I get an updated package automatically when there is a new release.
bus commented on 2018-10-11 17:19 (UTC) (edited on 2018-10-11 17:19 (UTC) by bus)
@karcher At this point I don't think it's possible -- there must be a reason to wait weeks to change the pkgver after every ZFS release.
I don't like being a whiny asshole about this again, but it has been a problem for too long. Having to submit a request to orphan the package every time it's been sitting out of date for a month doesn't really feel in line with the "bleeding edge" ways of Arch.
RubenKelevra commented on 2018-10-11 05:20 (UTC)
Looks like isiachi has too little time to update this and the zfs package in time :(
karcher commented on 2018-10-07 09:14 (UTC)
zfs-0.7.11 is compatible with 4.18 kernel. Is it possible to simply modify the pkgver and sha256sums accordingly in the PKGBUILD and install it?
adlerweb commented on 2018-09-25 08:47 (UTC)
0.7.11 has been released. Changing pkgver should be sufficient to get it working with current kernels.
minextu commented on 2018-09-10 09:07 (UTC)
@Kaedo As far as I know dkms-sorted is no longer necessary, since dkms in extra has this functionality now (https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/dkms&id=efcb54fb735b22c1bc405b255dbe9f8decc8bb8d).
About the kernel panic: We recently changed the hook a bit which might cause your boot problems. Please open an issue at http://github.com/archzfs/archzfs with more details (This AUR package is not archzfs).
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)