osc -A https://api.opensuse.org checkout filesystems/zfs && cd $_
Embed a build result badge whereever you need it. Select from
the options below and copy the result over to your README or on
your website, and enjoy it refresh automatically whenever the
build result changes.
This comment has been deleted
Since that is not a property of the zfs package, I can't change that.
It's also not needed because both 15.0 and 15.0:Update share the same kernel ABI.
I suggest you file a bug report with the openSUSE kernel guys. Apparently, no KMP whatsoever has the "ksym(....)" entities anymore (rpm -qR --provides zfs-kmp-default-...., rpm -qR --provides xtables-addons-kmp-..., etc.)
rpm -qR --provides zfs-kmp-default-....
rpm -qR --provides xtables-addons-kmp-...
That sounds like https://bugzilla.opensuse.org/show_bug.cgi?id=1110929
Has anyone set up such a project that can be shared?
I don't think it makes sense for everyone interested to establish their own project.
I gave it a try with latest Leap 15.0.
But unfortunately after installing zfs and a reboot all ZFS related services failed to start because the ZFS kernel modules were not loaded. :(
Distribution: openSUSE Leap 15.0
Name : kernel-default
Version : 4.12.14
Release : lp184.108.40.206
Install Date: Tue Feb 19 07:22:32 2019
x86_64 build failed?
Please update for tumbleweed kernel 4.20.x
Please update for tumbleweed kernel 5.0.x
Please update for tumbleweed kernel 5.1.x
Please update for production use.
I submitted an SR yesterday -- you can check the list of open SRs here and see whether it's necessary to send a reminder.
I just came across this: "ZFS allows anyone to use non modifying commands", see this discussion. It is especially interesting since this is supposed to work without any modifications to sudoers.
Other Linux distributions appear to package ZFS appropriately, but in case of openSUSE's filesystems project, the zfs and zpool commands reside in /usr/sbin and can therefore not be executed by non-root users. From openSUSE's perspective, first of all, is this a bug or intentional behavior?
zfs upstream installs it that way. If that way is incorrect, file a bug report with upstream.
Thanks - done.
See replies by ZFS developers upstream. The basic assumption appears to be that normal users should in general be allowed to run commands in /usr/sbin (hence normal users should for instance by default be able to run zfs list). My understanding is that this conflicts with openSUSE's design.
Hi, Today release ZoL 0.8.3
Currently, happen Tumbleweed build fail, please update.
Thanks for update to 0.8.3
but, Tumbleweed build still fail on Line 57 on zfs.spec, I guess package name generation fail?
Try on my Tumbleweed server.
/home/abuild/rpmbuild/BUILD/obj-default/include/spl/sys/time.h:88:15: error: unknown type name 'time_t'
Is there anything the community can do to help with things like this? Is there an easy way to figure out when things are an issue with Zol or with OpenSUSE's build service config (or something else)?
Normally I just roll back to a compatible kernel, to get zfs (kmp's, etc.) working again. But apparently that was clobbered with the recent dist update (I then set zypper to keep 3 older kernels. I suppose I should just turn that off, altogether, and try and remember to manually clean those, periodically).
Ok. I guess there's at least one person working on getting updated to 0.8.4. It looks like it, at least, builds for aarch64.
With the 0.8.4 update, I now get file conflicts when trying to upgrade from 0.8.3 (on Leap 15.1):
Detected 24 file conflicts:
from install of
conflicts with file from package
and so on, for every file in /lib/modules that is owned by zfs.
Hi I am testing Leap 15.2 on staging environment.
When start zfs build for 15.2?
I will try it.
Hi I tried zfs on Leap 15.2 beta, but cannot load zfs.ko and cannot start zfs filesystem.
sudo modprobe -vvv zfs
modprobe: INFO: custom logging function 0x5608c462c540 registered
modprobe: INFO: Failed to insert module '/lib/modules/5.3.18-lp152.14-default/extra/spl/spl.ko': Operation not permitted
modprobe: ERROR: could not insert 'zfs': Operation not permitted
modprobe: INFO: context 0x5608c5b90450 released
I use secure boot, module don't have signature?
Hi, Leap 15.2 Released!
I try modprobe zfs again but still have error.
sudo modprobe -vvvvv zfs
modprobe: INFO: custom logging function 0x555ea82f1540 registered
modprobe: INFO: Failed to insert module '/lib/modules/5.3.18-lp152.20.7-default/extra/spl/spl.ko': Operation not permitted
modprobe: ERROR: could not insert 'zfs': Operation not permitted
modprobe: INFO: context 0x555ea8f694f0 released
Module don't sign by default key?
Today test on non secure boot environment.
modprobe complete and can enable zfs service, but turn on secure boot again can not load zfs.ko.
chacek modinfo between 15.1 & 15.2 zfs & spl, I see same information.
I hope to use secure boot for security.
Sorry I am miss understand.
I add filesystem SSL cert to my MOK util.
I can load zfs.ko on secure boot environment!
I try upgrade my staging and main env!
I've created an openQA test for this and would appreciate feedback: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10873
i have 15.2, i tried the 0.8.4 build, won't install. i have glibc 2.26, this build wants 2.28. presumably your build server has a later glibc than 15.2. any advice?
You did not use the build for 15.2.
i don't know how i did it, but you're right. ty!
second question, hopefully less foolish. following your correction, i installed zfs from your 15.2 repo.
at no time during "zypper install zfs" did the system run mkinitrd, and the tools (zpool) asked me to
please run "modprobe zfs" which i did. systemctl was reporting similar errors for the zfs related
services. reboot did not change this situation, until i ran mkinitrd by hand and rebooted again, after
which everything worked fine.
as a long time user of freebsd, i am extremely impressed with the quality of ZoL. i've used suse for
many years -- it became my default linux distro when they sent me a free CDROM back in the mid
1990's as thanks for Cron. but only now with ZoL am i trying suse in a server role, and it's great.
Hi, ZoL 0.8.5 released.
but please do not use OpenZFS 2.0 RC version!
Thanks for quick response!!
I just updated from 15.1 to 15.2 and ran into the kernel lockdown "issue". I tried reinstalling entirely zfs and all the deps without any success and couldn't get zfs load until I disabled secureboot on the box. Is zfs not signed? Is there something that I've missed?
Have you use Secure boot?
if you use Secure boot, add filesystem repo key to MOK by mokutil.
I met same situation after 15.2 update, 15.2 is more strict key check than 15.1 or tumbleweed.
Oh great, thanks for the hint! For now I got around the lockdown by disabling SecureBoot which is not ideal.
Just to be clear you mean this key?
I could found key on "filesystem" project top page on few month ago.
But now I can't found key...
Paste key information (result of mokutil --list-enrolled)
SHA1 Fingerprint: a0:8e:c9:25:f6:31:39:96:6a:98:dd:a2:46:2c:05:f5:b2:a3:a2:93
Version: 3 (0x2)
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=filesystems OBS Project/emailAddressemail@example.com
Not Before: Nov 6 23:45:06 2020 GMT
Not After : Jan 15 23:45:06 2023 GMT
Subject: CN=filesystems OBS Project/emailAddressfirstname.lastname@example.org
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Exponent: 65537 (0x10001)
X509v3 Basic Constraints: critical
X509v3 Subject Key Identifier:
X509v3 Authority Key Identifier:
X509v3 Key Usage: critical
Digital Signature, Certificate Sign
X509v3 Extended Key Usage:
Signature Algorithm: sha256WithRSAEncryption
I find download link from my shell history.
You can download ssl certificate and convert x509 key
openssl x509 -in ssl_certificate -outform der -out cert.der
enroll mok key to mokutil and bootloader (phisycal machine access required)
sudo mokutil --import cert.der
Can you try?
Oh this is great, thank you!
Can't touch the server until the weekend though. Will let you know once it is done.
I did try it, but I can't boot with SecureBoot policy enabled. It just holds the system until I hit enter which is not ideal. There seem to be an issue with the signature and during boot, Leap does list an x509 error.
Unfortunately I couldn't keep the server off long enough to be able to debug, but holidays are coming up and planning to look into this a bit deeper.
Btw, is it ok to discuss issues here?
EDIT: Also found this: https://bugzilla.opensuse.org/show_bug.cgi?id=1173551
It is sad.
My leap server's dmseg around X.509 key.
[ 6.114200] Loading compiled-in X.509 certificates
[ 6.114229] Loaded X.509 cert 'openSUSE Secure Boot Signkey: c8bdc7ac1a1d85966217fd93ebfc14f4a200b814'
[ 6.114242] zswap: loaded using pool lzo/zbud
[ 6.114265] page_owner is disabled
[ 6.118823] Key type big_key registered
[ 6.121079] Key type encrypted registered
[ 6.121081] AppArmor: AppArmor sha1 policy hashing enabled
[ 6.121517] integrity: Loading X.509 certificate: UEFI:db
[ 6.121543] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[ 6.121543] integrity: Loading X.509 certificate: UEFI:db
[ 6.121564] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[ 6.122604] integrity: Loading X.509 certificate: UEFI:MokListRT
[ 6.123160] integrity: Loaded X.509 cert 'filesystems OBS Project: fd265e4d1ff97a9b0258b35833ce9e6b5aa7344b'
[ 6.123161] integrity: Loading X.509 certificate: UEFI:MokListRT
[ 6.123340] integrity: Loaded X.509 cert 'openSUSE Secure Boot CA: 6842600de22c4c477e95be23dfea9513e5971762'
Is it hint about your situation?
Appreciate your help, but it turns out that what you sent for the first time ssl and steps to import it to MOK actually worked. The bigger problem was that some other openSUSE key (valid, no funny business) apparently stuck in the bios. I assume from a previous installation. Removing that and booting the shim actually solved the problem...
Thank you for the help again!
Wondering if all this could be done just by zypper...
I try to add filesystem repo from clean install enviroment,
After install zfs package and reboot, mokutil boot menu display and can enroll repo key.
but It is only once if miss it boot failed...
Someone (zypper? or zfs rpm package?) call mokutil and enroll repokey (password is same as root password).
Another repo add to this environment, same mokutil boot mesu display.
I think iti is zypper function.
I'm completely new to OBS (and SUSE in fact) so perhaps I'm missing something, but is there a reason why zfs package is not being built for aarch64 on openSUSE Leap 15.2 while it works on SLE_15_SP2?
zfs-kmp-default needs to be updated for kernel 5.12.
sudo zypper update zfs-kmp-default
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: nothing provides kernel-uname-r = 5.11.16-1-default needed by zfs-kmp-default-2.0.4_k5.11.16_1-1.35.x86_64
Solution 1: do not install zfs-kmp-default-2.0.4_k5.11.16_1-1.35.x86_64
Solution 2: break zfs-kmp-default-2.0.4_k5.11.16_1-1.35.x86_64 by ignoring some of its dependencies
If this isn't the right place to post this, please let me know.
zfs-kmp-default was updated. Thanks!
Kernel update from 5.3.18-57-default to 5.3.18-59.5-default on Leap 15.3.
but no rebulid job on this repository.
update 5.3.18-59.5.2 from "Update repository with updates from SUSE Linux Enterprise 15" repo (not update-oss).
not detect source change from sle repo?
Thanks for update,
but on Leap 15.3 and SEL 15SP3 kmp version is still 5.3.18_57.
Is it OBS service problem?
Hi OpenZFS 2.1-rc7 released.
And please check Leap 15.3 repo not track kernel update.
I check another kmp repo, it have same problem, is is OBS config missmatch.
I check SLE15 SP3 repo, but same as Leap15.3...
Today(25/June) rebulid whlile zfs on Leap 15.3 and SLE 15 SP3, but still kmp for kernel 5.3.18-57-default.
Hi, OpenZFS 2.1.0-rc8 released.
rc7 have auto import failed bug.
this bug fixed on rc8, please update.
Hi OpenZFS 2.1.1 released.
Please update for Tumbleweed.
It's better to post to bugzilla.opensuse.org . OBS is not optimized for more than a few comments.
Agree, Next time, I will post to buglizza.
Thanks for advice.
Hello. I run openSUSE Tumbleweed with kernel 5.14.9 (newest one at the time of writing). I upgraded the system with zypper dist-upgrade today and I see that ZFS kernel modules were not rebuilt during the upgrade. I see that ZFS kernel modules are located in /lib/modules/5.14.6-2-default (previous kernel), but there are none in /lib/modules/5.14.9-1-default. Is filesystems/zfs package supposed to rebuild kernel modules between system updates? What am I missing here? (I'm new to openSUSE)
Also, I see that zfs-kmp-default-2.1.1_k5.14.6_2-1.25.x86_64 package is present in the system, which indicates that kernel modules were installed specifically for kernel 5.14.6. How can I rebuild/reinstall filesystems/zfs package for newest running kernel, and how to avoid this situation in the future?
Enabling Arm (64-bit) for Leap 15.3 for RaspPi usecases/zfs wich is referenced here https://en.opensuse.org/openSUSE:Raspberry_Pi, since 15.3 Arm is no longer build separately in ports but rather as 1st class citizen.
Looks like 15.4 is failing to build on the final release... I'm going to poke around but I have to work so don't rely on me please :)
EDIT: looks like kernel-devel may be missing asm/fpu/internal.h ...
Looks like this is failing for tumbleweed due to this -> https://github.com/openzfs/zfs/issues/13463 , which obviously hasn't made it into a release yet, so not sure there is anything that can be done...
Agreed, but the Suse 15.4 kernel should be supported in the current zfs release
I opened a bug for the missing kernel symbols, but still not 100% sure this is the root cause https://bugzilla.suse.com/show_bug.cgi?id=1200337
Looks like it is intentional.
I created a VERY dirty patch just removing the inclusion of the header in my home project just to get it working https://build.opensuse.org/package/show/home:hibby50:server/zfs
This is patched upstream in https://github.com/openzfs/zfs/commit/4c6526208db0d3d5abf44664e74d1e28156a3db7 but the diff does not apply cleanly to 2.1.4
This looks very promising. I took the liberty to run some openQA tests against your project and it looks sane so far: https://openqa.opensuse.org/tests/2410259
Would it be possible to build a DKMS-based version of this package?
The advantage of it would be that on updating the kernel, the ZFS kernel module would be automatically rebuilt against it, so it would keep working.
Hello team, could you please look into 15.5 situation? https://bugzilla.opensuse.org/show_bug.cgi?id=1203876 we seem to have a module load issue with what seems to be the non-fuse module. I'd be happy to see zfs tests suite passing again on Leap.
Hey, it appears the current build has been failing on tumbleweed for a while now, so trying to install zfs-kmp-default now fails with:
Problem: nothing provides 'kernel-uname-r = 6.2.6-1-default' needed by the to be installed zfs-kmp-default-2.1.9_k6.2.6_1-2.1.x86_64
Is there any update on this?
Unfortunately from what I can see this is still an open issue on the Open ZFS project. They've not had a new release that resolves this on 6.3. So I think we're stuck not updating until that comes out and then gets merged here.
Just a heads-up; OpenZFS 2.1.12 has released with kver6.3 compatibility.
The comment space is the wrong tool for reports. Use bugzilla.
The Open Build Service is an