Package Details: zfs-dkms-staging-git 2.3.0.r0.gbc06d8164b-3

Git Clone URL: https://aur.archlinux.org/zfs-dkms-staging-git.git (read-only, click to copy)
Package Base: zfs-dkms-staging-git
Description: Kernel modules for the Zettabyte File System (release staging branch) with compatibility patches for latest stable kernel.
Upstream URL: https://zfsonlinux.org/
Licenses: CDDL-1.0
Groups: zfs-staging-git
Conflicts: zfs-dkms
Provides: SPL-MODULE, zfs, zfs-dkms, ZFS-MODULE
Submitter: bjin
Maintainer: bjin (darkbasic)
Last Packager: bjin
Votes: 10
Popularity: 0.86
First Submitted: 2024-01-15 11:23 (UTC)
Last Updated: 2025-01-14 13:40 (UTC)

Dependencies (4)

Required by (20)

Sources (4)

Latest Comments

1 2 3 4 5 6 Next › Last »

darkbasic commented on 2025-01-14 13:04 (UTC)

Awesome, thank you!

bjin commented on 2025-01-14 11:06 (UTC)

updated to include an alpm-hook to warn package user about unsupported kernel versions

bjin commented on 2025-01-14 08:03 (UTC)

@darkbasic: Well, I get your point.

The main reason this package ("-staging-git") existed, is that there are times new kernel released but latest zfs stable released failed to compile against it. Staging branches usually contains some compat patches (but not always). In this case, "Linux-Maximum" section specified in META file is supposed to be ignored. That's the reason I added this flag.

But I agree that we should ideally warn package user about this. Maybe a one-time warning during package installation or a alpm trigger that verify the kernel version for each kernel and zfs upgrade. Which one do you think works the best?

darkbasic commented on 2025-01-14 07:33 (UTC)

While enabling it is probably the right thing to do please everybody be careful with --enable-linux-experimental since zfs 2.3 didn't pass the test suite against 6.13 yet.

darkbasic commented on 2024-12-12 07:30 (UTC)

Awesome, thank you!

bjin commented on 2024-12-12 03:13 (UTC)

Updated to 2.2.7 stable release

@darkbasic: fyi, I removed all backported patches. All of these patches seems to be merged in 2.2.7 (either ignored, or causing conflicts during patching)

darkbasic commented on 2024-11-21 07:36 (UTC)

Oh my bad, I keep forgetting that AUR helpers refuse to re-download patches if the name stays the same. These two were patches taken directly from upstream, but since master is starting to diverge a lot from 2.2.x most of them require backporting and so I've decided to pick these two from my backports as well since they were the only outliers and they apply more cleanly anyway. Now I've renamed them and it should work without having to clean your cache.

spacemann commented on 2024-11-21 07:16 (UTC)

I'm getting failed checksums with this package right now:

:: Downloading PKGBUILDs...
 (1/1) zfs-dkms-staging-git-2.2.6.r0.gbaa5031456-3   [--------------------------------------------------------------------------------]fetching devel info...
==> Making package: zfs-dkms-staging-git 2.2.6.r0.gbaa5031456-3 (Thu 21 Nov 2024 02:07:32 AM EST)
==> Retrieving sources...
  -> Updating zfs git repo...
  -> Found linux610-zfs_log-add-flex-array-fields-to-log-record-structs.patch
  -> Found linux610-fix-tracepoints-definitions.patch
  -> Found linux610-lua-add-flex-array-field-to-TString-type.patch
  -> Found linux612-avoid-kmem_cache_create-redefinition.patch
  -> Found linux612-support-3arg-dequeue_signal-without-task-param.patch
  -> Found linux612-FMODE_UNSIGNED_OFFSET-is-now-FOP_UNSIGNED_OFFSET.patch
  -> Found linux612-f_version-removed-from-struct-file.patch
  -> Found linux612-PG_error-flag-was-removed.patch
  -> Found 0001-only-build-the-module-in-dkms.conf.patch
==> Validating source files with sha256sums...
    zfs ... Skipped
    linux610-zfs_log-add-flex-array-fields-to-log-record-structs.patch ... Passed
    linux610-fix-tracepoints-definitions.patch ... FAILED
    linux610-lua-add-flex-array-field-to-TString-type.patch ... FAILED
    linux612-avoid-kmem_cache_create-redefinition.patch ... Passed
    linux612-support-3arg-dequeue_signal-without-task-param.patch ... Passed
    linux612-FMODE_UNSIGNED_OFFSET-is-now-FOP_UNSIGNED_OFFSET.patch ... Passed
    linux612-f_version-removed-from-struct-file.patch ... Passed
    linux612-PG_error-flag-was-removed.patch ... Passed
    0001-only-build-the-module-in-dkms.conf.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'zfs-dkms-staging-git-2.2.6.r0.gbaa5031456-3':
error: packages failed to build: zfs-dkms-staging-git-2.2.6.r0.gbaa5031456-3

Seniux commented on 2024-11-20 21:03 (UTC)

No, typical oficial Arch linux kernels. Same system configuration, but hardened does not loading. I tried to find info on the internet, and this is only my gues that this bug can be the same. How to reproduce? Simple install linux-hardened + linux-hardened-headers, regenerate mkinicpio and try to boot hardened kernel.

darkbasic commented on 2024-11-20 19:49 (UTC)

Do you use CONFIG_RANDSTRUCT=y? If so I don't think there is anything we can do to fix it.

1 2 3 4 5 6 Next › Last »