Package Details: zfs-linux-git-headers 2.1.99.r1298.g6fca6195cd-1

Git Clone URL: https://aur.archlinux.org/zfs-linux-git.git (read-only, click to copy)
Package Base: zfs-linux-git
Description: Kernel headers for the Zettabyte File System.
Upstream URL: https://zfsonlinux.org/
Licenses: CDDL
Conflicts: spl-dkms, spl-dkms-git, spl-headers, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-headers
Provides: spl-headers, zfs-headers, zfs-linux-headers
Submitter: demizer
Maintainer: severach
Last Packager: severach
Votes: 24
Popularity: 0.000062
First Submitted: 2016-04-21 08:46 (UTC)
Last Updated: 2022-10-09 15:24 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

demizer commented on 2017-12-18 22:01 (UTC)

I do see the systmed scripts are missing in the zfs-utils-common-git packages. I will fix and update.

ArnoW commented on 2017-12-18 21:50 (UTC)

After updating to zfs-linux-git 2017.12.18.r3214.bbffb59ef.4.14.6.1-1 the systemd services for zfs are gone. Is there a bug in the package or am I missing something?

lockheed commented on 2017-09-27 17:49 (UTC)

Why is it that this git package has version 0.7.0, while the "stable" non-git zfs-linux is 0.7.2? Wasn't git version supposed to be newer than the mainline?

sfranchi commented on 2017-09-21 16:59 (UTC)

Well, ignore my previous comment, I misread pacman's error message. Sorry for the noise

sfranchi commented on 2017-09-20 17:18 (UTC)

@minextu: You suggested using pacman -Syuu to overcome the misleading versioning info. However, with the suggested option (the uu), pacman wants me to switch from zfs-linux-git to zfs-linux. Ideas?

minextu commented on 2017-08-02 21:36 (UTC)

@dmp1ce Now that zfs 0.7 is out, there aren't any rc packages any more, but pacman assumes, that the rc version is higher than the current one. You will have to run # pacman -Syuu

dmp1ce commented on 2017-08-02 21:33 (UTC)

What's going on with the versioning? I am getting this warning: $ pacaur -Syu :: Synchronizing package databases... core is up to date extra is up to date community is up to date archzfs is up to date :: Starting full system upgrade... warning: spl-linux-git: local (0.7.0_rc4_r5_g7a35f2b_4.11.9_1-1) is newer than archzfs (0.7.0_r1_geed143d_4.12.3_1-2) warning: zfs-linux-git: local (0.7.0_rc4_r95_g94b25662c_4.11.9_1-1) is newer than archzfs (0.7.0_r6_g1e0565d10_4.12.3_1-2) resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: spl-linux-git: installing linux (4.12.3-1) breaks dependency 'linux=4.11.9-1' :: zfs-linux-git: installing linux (4.12.3-1) breaks dependency 'linux=4.11.9-1' :: zfs-utils-linux-git: installing linux (4.12.3-1) breaks dependency 'linux=4.11.9-1' :: Starting AUR upgrade... :: spl-utils-linux-git is not present in AUR -- skipping :: zfs-utils-linux-git is not present in AUR -- skipping :: resolving dependencies... :: looking for inter-conflicts...

Karmek commented on 2017-07-30 18:47 (UTC) (edited on 2017-07-30 18:49 (UTC) by Karmek)

Hello @Demizer! The package version used to be 0.7.0_rc4_r5 and now fails to resolve the required dependencies as it considers the local packages as newer than what's available. There is no update triggered for zfs-linux-git, spl-linux-git etc. Please consider updating the version number accordingly (i.e. version 0.7.1_r1).

wolfdogg commented on 2017-01-29 20:47 (UTC) (edited on 2017-01-29 21:31 (UTC) by wolfdogg)

following up on this Zenju the author of freefilesync has corroborated that my suspicions were correct http://www.freefilesync.org/forum/viewtopic.php?f=2&t=1650&p=13710#p13710, the flag is on somehow on the zfs filesystem possibly, or maybe missing one, and these errors persist. This is NOT the ARCH pkg in anyway. Im using RHEL64 7.3 to run the san which uses zfsonlinux/zfs https://github.com/zfsonlinux/zfs/ using the kABI-tracking kmod (so that i dont have to futz with improper kernel updates anymore). So with that said, if anybody knows how to tweak the zfs properties/settings as such so that SPARSE is set OFF, im all ears. Thats where my research is going to next. Im not sure what i might have done, this is a standard raidz2, and havent had luck with any other pool testing yet. Is this a bug, or not a bug? @demizer Any ideas?