@eblau we are talking about a change to configure.ac
, not a 6.9 support (which is clearly not there and it makes sense it's only available in VCS package).
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)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 66 Next › Last »
thaewrapt commented on 2024-07-10 15:14 (UTC) (edited on 2024-07-10 15:14 (UTC) by thaewrapt)
eblau commented on 2024-07-10 15:04 (UTC)
@thaewrapt https://wiki.archlinux.org/title/Arch_Linux
Arch Linux defines simplicity as without unnecessary additions or modifications. It ships software as released by the original developers (upstream) with minimal distribution-specific (downstream) changes: patches not accepted by upstream are avoided, and Arch's downstream patches consist almost entirely of backported bug fixes that are obsoleted by the project's next release.
Adding support for a newer kernel release than the upstream ZFS release is not a "bug fix".
thaewrapt commented on 2024-07-10 14:44 (UTC)
@yurikoles can you point out where in the package guidelines is that? Because this is an actual purpose of PKGBUILD scripts, to have and apply patches that are needed but still not available upstream.
darkbasic commented on 2024-07-10 14:39 (UTC)
@mabod zfs-dkms-staging-git follows latest stable branch and has support for latest kernel plus backported fixes for new kernels (like the zvol issue with 6.9).
yurikoles commented on 2024-07-10 14:37 (UTC)
@mabod
The Arch Linux way is to keep packages as close to vanilla state as possible. So the best option here is to wait for the next release with that fix. Or we may end up backporting half of the next release commits.
mabod commented on 2024-07-10 07:49 (UTC)
The zfs stuff is not cleanly uninstalled when I remove a kernel. There are leftovers in /usr/lib/modules/KERNEL/build. See also this issue for zfs: https://github.com/openzfs/zfs/issues/16221 This seems to be an issue with automake as explained by the dksm developers: https://github.com/dell/dkms/issues/418 The solution should be to add "no-dependencies" into configure.ac https://www.gnu.org/software/automake/manual/automake.html#Dependencies Is that something that could be added to the PKGBUILD?
itoffshore commented on 2024-07-08 19:36 (UTC)
@sphere101 - keep an eye on zfs
releases for kernel support
sphere101 commented on 2024-07-08 17:18 (UTC)
Hello, Any update on when zfs-dkms will be updated to support kernel 6.9.x? Thank you.
mabod commented on 2024-06-22 13:42 (UTC)
@sausix: in the past you could compile zfs for a non supported kernel and if the compilation was successful you could use zfs for the unsupported kernel and eventually end up with data corruption. Thats the reason why the devs have implemented a check that prevents compilation for unsupported kernel version. You have seen this message when you tried to compile for kernel 6.9. zfs is always lagging behind kernel version support. This lies in the nature of the out-of-tree development process. There is nothing to be frightend about. Love it or leave it.
sausix commented on 2024-06-22 12:52 (UTC)
@mabod I've read about the warning yesterday. Some people call it "danger zone" and I picked the term up here (subconciously): https://github.com/openzfs/zfs/pull/15931 Someone had a corruption already. The kernel devs probably don't care for breaking changes to ZFS. And they won't break it on purpose.
@itoffshore linux-lts sounds reasonable. linux-hardened is on 6.9.5 too and exceeds the maximum kernel version: Linux-Maximum: 6.8
Most people will use ZFS with older kernels because of lts or just having an old kernel on their NAS boxes I guess.
I know. Always have a backup. But it still may corrupt my new unbackupped data. I want to try RaidZ expansion which is experimental enough.
I definitely will use linux-lts but I'm still wondering it isn't recommended here at least. The warning and the huge kernel version difference is frightening enough for me.
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)