Dear Maintainer,
zfs system is completely non-functional due to zfs-dkms kernel module
compilation terminating in error.
My `/home/` is on zfs and thus I'm restricted to use `root` who has
a usable `$HOME`.
* What led up to the situation?
Routine "apt update && apt upgrade", most likely due to kernel upgrade.
After installation system asked for a reboot to complete kernel update.
After reboot I got the normal `lightdm` login screen, but I was unable
to login.
I went to a text console to analyze situation and I found /home/ completely
wiped.
Also dmesg shows system does not find suitable ZFS moduled and thus is
unable to mount pool.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried to reinstall the failing package, but there are evident errors
visible in `/var/lib/dkms/zfs/2.1.4/build/make.log`
I am unsure how I can attach the file here.
If I don't manage it I will try to comment on the bug from another machine.
System is currently completely unusable.
Apparently root cause is function `bio_alloc()` changed signature qith newer kernels 5.17.x -> 5.18.0. Apparently upstream sources were not updated; specifically file `.../zfs/vdev_disk.c` still uses the old (2 parameter) function instead of the newer (4 parameters) one. I will report also upstream. Regards Mauro
Hi. This build here from Ubuntu Launchpad contains all patches (19) for a successful build. https://ppa.launchpadcontent.net/vicamo/ppa-1971456/ubuntu/pool/main/z/zfs-linux/zfs-linux_2.1.4-0ubuntu0.2.debian.tar.xz ...
I am also affected by this. I did simple apt update and apt upgrade and now I can't use my zfs volume anymore.
found 1012600 2.1.4-1 thanks Module compilation (5.18) stalls for 10-15 minutes, then errors out. Make log attached.
Apologies if this question is well-answered, but why isn't this package holding back the kernel to 5.17? In my mind an "apt upgrade" should not have pulled 5.18, especially when the net result may well be an unbootable system. Surely there's some way to mark this package as broken in tandem with 5.18? I'm also quite surprised this wasn't caught in sid before it was pulled into testing. Is there any form of testing for this package going on in sid?
I'm no expert, but since these packages are in 'contrib' I suspect they don't have the ability to block package upgrades in 'main'.
packages, your existing kernel package is satisfying the dependency.
We believe that the bug you reported is fixed in the latest version of
zfs-linux, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1012600@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mo Zhou <lumin@debian.org> (supplier of updated zfs-linux package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Wed, 22 Jun 2022 20:48:20 -0700
Source: zfs-linux
Architecture: source
Version: 2.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers <pkg-zfsonlinux-devel@alioth-lists.debian.net>
Changed-By: Mo Zhou <lumin@debian.org>
Closes: 1012600
Changes:
zfs-linux (2.1.5-1) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Switch to dh-sequence-dkms.
* Do not use deprecated dkms feature REMAKE_INITRD.
* Switch to autopkgtest-pkg-dkms.
* Do not attempt to build the modules on PREEMPT_RT kernels. (cf. #981212)
.
[ Mo Zhou ]
* New upstream version 2.1.5 (June 2022) (Closes: #1012600)
* Remove merged patches:
- 4900-ppc-get-user-workaround.patch
- 4901-zvol_wait-Ignore-locked-zvols.patch
- no-REMAKE_INITRD.patch
And Rebase all remaining patches.
.
[ Alejandro R. Sedeño ]
* zfs-dracut: install new man page
* refresh symbols
Checksums-Sha1:
a54cda0bec6e3b547cd9245e149fe6bedae5aadb 3534 zfs-linux_2.1.5-1.dsc
bfc2ed0cf2d339164d7865b421c9e34044c96fd3 34951632 zfs-linux_2.1.5.orig.tar.gz
478141a2002a0ae33e5192169c381eb91feb4e22 100568 zfs-linux_2.1.5-1.debian.tar.xz
54e9c21ee05fcef135e5204049742f047a9b6ed7 9917 zfs-linux_2.1.5-1_source.buildinfo
Checksums-Sha256:
e3e547fad03cc1d8fab0f657f11b0ec0d7abc3509c417a6dfd5243897e825637 3534 zfs-linux_2.1.5-1.dsc
1913041e5c44ff07ca384346ad8145aeedf77e77cd1cea9ec5d533246691e10c 34951632 zfs-linux_2.1.5.orig.tar.gz
36a833d51877b7a68925b3f827634d915e8f41ab77057ecde65d63bb743f72b9 100568 zfs-linux_2.1.5-1.debian.tar.xz
4bc2e48aacd38d1882c669f352233ce446a23cb9b4a775317293f2d59c9e4f92 9917 zfs-linux_2.1.5-1_source.buildinfo
Files:
dc9f1764af2ec99c5e9093e638b38872 3534 contrib/kernel optional zfs-linux_2.1.5-1.dsc
a1efd694cfa22522c51400b2e8731f25 34951632 contrib/kernel optional zfs-linux_2.1.5.orig.tar.gz
5bdf31bf7194581d415f337f83911e52 100568 contrib/kernel optional zfs-linux_2.1.5-1.debian.tar.xz
270cbc07fd561d85332d5076eb60fb58 9917 contrib/kernel optional zfs-linux_2.1.5-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmKz4wURHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaopTtw/+OKnFEp3ICSzwSILvMI3kTfAcacI/FmI0
ep2f3KOhexhd7uGhLrPOt2YH0brWg5s8KOYYc/8lLylYupBzpIpef3c1of94AAEm
WupdKyssIhaDbzw2OthCiRifEiHx9YVN1F71HagpGaxQLlSXyG5WBfCZsv6fxGb3
BxAjT04W8YNP5x4OBnGLujeci+JLQ3MYuqXfAth+T3U2Bki/TfIg4C2+xuA+WAP5
jXKdHQE3SSZLSbvVic0m0ZpqRfEYBZn3rNqzOzXor1+j8BU/T7Zo7RsQEjj9MhXi
k0a9WAzHqmDilAIXouYn05YZ6VwP3nlHxnPdTzIGep7nLIXnWk2K8xtjRioG6L0z
feKtsyPmh2F0Fgzfgq4dgFIciXVmGLgvQUCD68vUu6T9iYEXz1oAfftdJFl45kxb
FqSo76yIC8v/f88C6dMS6Y5tHZ1yn2ElzrOXs+fr9Ru3qp0he2i9RlKVfW4+jg5p
eOx0N8c2cOV2v4W7SEiMI61jn0lT5Jfmr0tK54zy+S00QCbAx0Fxc4T9w2LDuv+M
ACNZruKsS4+xjMWcSuESEa4Y0LG78gH8wpkQ/L5i6dIEfbmRPHjXFnSqzOrLOsxX
Nelgf6S12Gjbm3BOZ7FhgFPaAOENQfLdsgF8JI9G2mxhyIyay4BUGHHg/Wr8TRxk
INNcjLTmcsE=
=oooz
-----END PGP SIGNATURE-----
On Thu, 23 Jun 2022 04:06:10 +0000 Debian FTP Masters <ftpmaster@ftp-master.debian.org> wrote: > Source: zfs-linux > Source-Version: 2.1.5-1 > Done: Mo Zhou <lumin@debian.org> > > We believe that the bug you reported is fixed in the latest version of > zfs-linux, which is due to be installed in the Debian FTP archive. For those of you who are using bookworm/testing and don't want to wait for the packages to drop from sid/unstable, you can download the sid/unstable packages as .deb files and install them yourself. This is potentially dangerous so don't proceed if you can wait. I have installed: zfs-dkms, zfsutils-linux and zfs-zed. By starting at the top I found the dependencies. Below are the files in the order I had success with. I installed: sudo dpkg -i /tmp/zfs/libnvpair3linux_2.1.5-1_amd64.deb sudo dpkg -i /tmp/zfs/libuutil3linux_2.1.5-1_amd64.deb sudo dpkg -i /tmp/zfs/libzfs4linux_2.1.5-1_amd64.deb sudo dpkg -i /tmp/zfs/libzpool5linux_2.1.5-1_amd64.deb sudo dpkg -i /tmp/zfs/zfsutils-linux_2.1.5-1_amd64.deb The last failed but only because it was waiting for the next package: sudo dpkg -i /tmp/zfs/zfs-dkms_2.1.5-1_all.deb I next reinstalled the one that failed on the assumption that it might not be totally finished sudo dpkg -i /tmp/zfs/zfsutils-linux_2.1.5-1_amd64.deb sudo dpkg -i /tmp/zfs/zfs-zed_2.1.5-1_amd64.deb A quick reboot, but zfs did not restart. I found in the syslog: Import ZFS pools by cache file was skipped because of a failed condition check (ConditionFileNotEmpty=/etc/zfs/zpool.cache) I found a fix: sudo zpool import -a After this I am able to use zfs in testing on linux 5.18. I don't know if I will have to repeat "zpool import -a" at my next reboot, but it seems like it is a possibility. I want to make clear I have no more than a superficial understanding of why this worked, nor do I know what the implications of hand-installing packages will be on later updates. Use this information at your own risk.
The 2.1.5 packages have made their way into bookworm, and my system is now happily running kernel 5.18 with ZFS.