Show filesystems / zfs - openSUSE Build Service

very thanks!

x86_64 build failed?

https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.8.0-rc3

ZFS-0.8.0-rc3 released.

Please update for tumbleweed kernel 4.20.x

Thanks

Why failed? spec file.

Thanks!!!

https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.8.0-rc4

ZFS-0.8.0-rc4 released.

Please update for tumbleweed kernel 5.0.x

Thanks!!!

https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.8.0-rc5

ZFS-0.8.0-rc5 released.

Please update for tumbleweed kernel 5.1.x

Thanks!

https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.8.0

ZFS-0.8.0 released.

Please update for production use.

Aleksa Sarai (cyphar) - over 5 years ago

I submitted an SR yesterday -- you can check the list of open SRs here and see whether it's necessary to send a reminder.

Sebastian Ernst (smernst) - over 5 years ago

Thanks！

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?

Jan Engelhardt (jengelh) - over 5 years ago

maintainer

zfs upstream installs it that way. If that way is incorrect, file a bug report with upstream.

Sebastian Ernst (smernst) - over 5 years ago

Thanks - done.

Sebastian Ernst (smernst) - over 5 years ago

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.

Michiya Hagimoto (kokeko) - almost 5 years ago

Hi, Today release ZoL 0.8.3

https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.8.3

Currently, happen Tumbleweed build fail, please update.

Michiya Hagimoto (kokeko) - almost 5 years ago

Thanks for update to 0.8.3

but, Tumbleweed build still fail on Line 57 on zfs.spec, I guess package name generation fail?

Michiya Hagimoto (kokeko) - almost 5 years ago

Thanks!

Try on my Tumbleweed server.

Brian Klahn (briandk) - over 4 years ago

/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).

Thanks.

Brian Klahn (briandk) - over 4 years ago

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. https://build.opensuse.org/package/rdiff/home:maelask:branches:filesystems/zfs?opackage=zfs&oproject=filesystems&rev=2

Hi I am testing Leap 15.2 on staging environment. When start zfs build for 15.2?

Thanks! 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 insmod /lib/modules/5.3.18-lp152.14-default/extra/spl/spl.ko 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 insmod /lib/modules/5.3.18-lp152.20.7-default/extra/spl/spl.ko 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.

Felix Niederwanger (ph03nix) - about 4 years ago

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 Thanks :-)

Paul Vixie (paulvixie) - about 4 years ago

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?

Jan Engelhardt (jengelh) - about 4 years ago

maintainer

You did not use the build for 15.2.

Paul Vixie (paulvixie) - about 4 years ago

i don't know how i did it, but you're right. ty!

Paul Vixie (paulvixie) - about 4 years ago

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.

Michiya Hagimoto (kokeko) - about 4 years ago

Hi, ZoL 0.8.5 released.

https://github.com/openzfs/zfs/releases/tag/zfs-0.8.5

Currently, happen Tumbleweed build fail, please update.

but please do not use OpenZFS 2.0 RC version!

Michiya Hagimoto (kokeko) - about 4 years ago

Thanks for quick response!!

Attila Pinter (adathor) - almost 4 years ago

Hi, 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?

Michiya Hagimoto (kokeko) - almost 4 years ago

Have you use Secure boot? if you use Secure boot, add filesystem repo key to MOK by mokutil.

https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-uefi.html

I met same situation after 15.2 update, 15.2 is more strict key check than 15.1 or tumbleweed.

Attila Pinter (adathor) - almost 4 years ago

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?

Michiya Hagimoto (kokeko) - almost 4 years ago

I could found key on "filesystem" project top page on few month ago.

https://build.opensuse.org/project/show/filesystems

But now I can't found key...

Paste key information (result of mokutil --list-enrolled)

[key 1] SHA1 Fingerprint: a0:8e:c9:25:f6:31:39:96:6a:98:dd:a2:46:2c:05:f5:b2:a3:a2:93 Certificate: Data: Version: 3 (0x2) Serial Number: cf:ae:ee:5c:71:9a:e9:de Signature Algorithm: sha256WithRSAEncryption Issuer: CN=filesystems OBS Project/emailAddress=filesystems@build.opensuse.org Validity Not Before: Nov 6 23:45:06 2020 GMT Not After : Jan 15 23:45:06 2023 GMT Subject: CN=filesystems OBS Project/emailAddress=filesystems@build.opensuse.org Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit) Modulus: 00:cb:09:7e:af:b0:aa:39:c7:02:e6:6e:91:79:80: 61:e8:80:92:6c:ea:ce:d6:33:52:f0:b2:32:62:c5: 32:1b:b8:3e:8b:4d:77:63:65:92:95:0a:0d:b7:9d: a2:be:9f:6b:90:84:b9:83:89:54:ff:05:a7:c7:86: d1:c4:5c:a1:ce:6c:1c:6a:54:35:aa:ae:ba:0c:41: 9a:c2:f8:eb:cc:8f:3b:ae:d1:11:48:d1:eb:1b:52: f6:6d:0e:f8:4c:c1:ed:aa:d4:22:59:70:c2:22:a1: fc:01:4d:31:80:73:19:58:95:56:ed:74:c3:91:1a: f2:32:eb:cd:7a:28:db:dc:d1:51:f3:ae:95:37:f0: 84:de:67:eb:b4:3c:54:6b:30:4d:2f:49:90:08:7f: 9a:64:cc:32:35:81:9f:ac:9f:75:ca:22:dd:3e:98: 75:2e:be:30:3c:f0:70:b7:35:3e:81:d0:e8:ea:93: 2e:d4:78:37:af:a6:bf:a6:9e:d4:b3:75:4e:73:ae: 77:d9:43:44:b1:63:9d:da:1e:98:16:19:c6:42:0f: 93:ed:c5:25:87:9c:13:c7:c0:c5:c8:53:e2:ed:65: 5a:a2:25:68:bd:61:f6:00:86:f8:51:4d:b0:54:63: 56:21:9b:79:41:40:f3:c6:74:2c:f7:82:24:8c:63: 29:85 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Basic Constraints: critical CA:FALSE X509v3 Subject Key Identifier: FD:26:5E:4D:1F:F9:7A:9B:02:58:B3:58:33:CE:9E:6B:5A:A7:34:4B X509v3 Authority Key Identifier: keyid:FD:26:5E:4D:1F:F9:7A:9B:02:58:B3:58:33:CE:9E:6B:5A:A7:34:4B

        X509v3 Key Usage: critical
            Digital Signature, Certificate Sign
        X509v3 Extended Key Usage:
            Code Signing
Signature Algorithm: sha256WithRSAEncryption
     27:80:26:e6:57:d5:c0:06:05:f3:bb:59:22:b0:e0:91:d2:ed:
     71:7c:e5:38:a7:5a:c9:53:41:73:13:1e:13:b0:63:c9:67:c4:
     af:49:18:fe:b0:cb:65:d9:82:a5:67:cd:f9:d3:28:67:f9:9b:
     b8:b1:b3:b5:ee:f6:e0:28:71:2d:6f:f8:09:3d:48:62:96:82:
     2d:60:e1:4d:2b:e7:b3:f9:70:69:d5:1d:50:92:93:86:3f:dc:
     1a:eb:b9:f3:54:fd:c2:a4:02:a6:32:39:cb:d4:af:6e:6a:91:
     32:c3:51:35:15:a5:71:02:9f:88:77:7a:e4:86:26:ce:fb:35:
     23:16:4f:50:4c:ac:65:64:e0:16:9a:7a:6d:11:55:ec:35:3e:
     26:f0:da:3b:de:5b:79:9a:f8:21:13:ce:4f:01:b7:3f:91:65:
     41:59:9a:0e:62:08:df:27:68:4d:59:bb:75:d2:88:d4:05:74:
     43:98:a9:d1:09:bc:99:6f:b3:45:28:b3:74:c3:b0:ff:e8:0f:
     00:7c:4d:7a:40:35:ba:59:62:9b:84:e6:49:bf:e4:20:83:f4:
     20:5b:c6:14:34:a3:1b:aa:25:de:9d:a5:7c:95:d7:5c:9c:d3:
     3b:86:aa:b4:63:a4:d8:9c:5a:a2:07:9b:6c:15:60:0a:20:ce:
     6c:43:2d:1f

Michiya Hagimoto (kokeko) - almost 4 years ago

I find download link from my shell history.

https://build.opensuse.org/projects/filesystems/ssl_certificate

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?

Attila Pinter (adathor) - almost 4 years ago

Oh this is great, thank you! Can't touch the server until the weekend though. Will let you know once it is done.

Attila Pinter (adathor) - over 3 years ago

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

Oh... 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?

Attila Pinter (adathor) - over 3 years ago

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...

Good!

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.

Michał B (michu) - over 3 years ago

Hello. 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?

Jared ABQLUG (Alucard) - over 3 years ago

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.

Jared ABQLUG (Alucard) - over 3 years ago

zfs-kmp-default was updated. Thanks!

Hi 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.

something wrong?

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?

https://github.com/openzfs/zfs/releases/tag/zfs-2.1.0-rc7

Hi OpenZFS 2.1-rc7 released.

Please update.

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.

Something wrong?

https://github.com/openzfs/zfs/releases/tag/zfs-2.1.0-rc8

Hi, OpenZFS 2.1.0-rc8 released.

Please update.

rc7 have auto import failed bug.

this bug fixed on rc8, please update.