Scratch my previous comment. It just takes a significant amount of time to install the module. Other DMKS modules I have installed take 10-15 seconds. ZFS takes around 10-15 minutes. I've no idea why this is but is why it appears to hang during a kernel upgrade. It doesn't hang, it just takes a lot longer than I'd expect.
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.47 |
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)
Latest Comments
« First ‹ Previous 1 .. 42 43 44 45 46 47 48 49 50 51 52 .. 66 Next › Last »
Tom_B commented on 2019-12-20 23:04 (UTC)
Tom_B commented on 2019-12-16 13:40 (UTC)
Every time I get a kernel update, the dkms install hangs:
: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Install DKMS modules
==> dkms install zfs/0.8.2 -k 5.4.3-arch1-1
Previously, ctrl-c to exit exited the install and I could modprobe zfs as expected. Now though I get this error:
Error! Bad return status for module build on kernel: 5.4.3-arch1-1 (x86_64)
Consult /var/lib/dkms/zfs/0.8.2/build/make.log for more information.
The log it mentions:
DKMS make.log for zfs-0.8.2 for kernel 5.4.3-arch1-1 (x86_64)
Mon 16 Dec 13:36:46 GMT 2019
make: Entering directory '/var/lib/dkms/zfs/0.8.2/build/module'
make: *** No targets specified and no makefile found. Stop.
make: Leaving directory '/var/lib/dkms/zfs/0.8.2/build/module'
Do I just need to wait for an update or am I missing something?
archfroggy commented on 2019-11-14 15:11 (UTC)
Hi, quick noob question. I am currently using zfs-dkms-git and want to switch back to zfs-dkms on an encrypted ZFS root. Everytime I try this I cannot boot anymore and I am dropped into the emergency shell with "filesystem 'rpool/ROOT/arch' can not be mounted: Permission denied". I can mount the pool inside the emergency shell just fine. Any ideas on how to fix this would greatly appreciated! Thanks
eschwartz commented on 2019-10-02 01:12 (UTC)
@Y5Lf8U0y5wFg4ktU is correct, the packages are designed so that you can build them without the other installed, but you need to pacman -U them both at the same time when upgrading. Most AUR helpers don't know how to do that, so you could try looking for one that does know how. Off the top of my head, aurutils does know how to behave properly here.
Y5Lf8U0y5wFg4ktU commented on 2019-10-01 09:36 (UTC)
It is easiest to build both packages and then upgrade them both at the same time. No need to remove anything.
If you use yaourt, just ignore the pacman errors, the packages will remain in your temp dir. Afterwards install them from there.
sphere101 commented on 2019-09-30 19:50 (UTC)
Had to remove both pacakges, then re-install utils and then zfs-dkms... Thanks
dharrigan commented on 2019-09-30 18:53 (UTC)
Hi,
It's pretty safe to remove the zfs-utils package then install the new version. It won't damage any zfs installation you have. I do it now and again!
Of course, don't trust any random stranger posting here, do test beforehand (if possible!). All I can say is that when I went from zfs 0.8.1 to zfs 0.8.2, I had to remove the previous dkms (things are still in-memory, so zfs still works), then just reinstall the ones that where upgraded...
fryfrog commented on 2019-09-30 16:21 (UTC) (edited on 2019-09-30 16:22 (UTC) by fryfrog)
Are you maybe using archzfs/zfs-dkms and now you're trying to install aur/zfs-dkms? I had this issue when I was trying to switch from one to the other. I just removed zfs-utils and then specifically installed aur/zfs-dkms which pulled in aur/zfs-utils correctly. I had to go back to archzfs/zfs-dkms though, due to difference in the initcpio stuff. :(
sphere101 commented on 2019-09-30 16:19 (UTC)
A bit of a noob question, Trying to upgrade with yay and running into dependencies with zfs-util.. resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing zfs-utils (0.8.2-2) breaks dependency 'zfs-utils=0.8.1' required by zfs-dkms
Any recommendations?
eschwartz commented on 2019-09-27 00:08 (UTC)
I indeed just saw the new zfs 0.8.2 release, but at the moment the tarball is missing a PGP signature.
https://github.com/zfsonlinux/zfs/pull/9161#issuecomment-535729519
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
validpgpkeys
array. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheck
argument tomakepkg
when building. (not recommended)