-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No kABI-tracking kmod for RHEL-based Linux 9.5 #16790
Comments
I'm running on RHEL 9.5 using rpm's generated according to those instructions. The only problem I had was getting it to install. If you are upgrading from 9.4 and you have the same version of ZFS already installed, installing the rpms built under 9.5 won't do anything, because they have the same name as the 9.4 ones and dnf thinks they're already installed. I had to do a reinstall, which unfortunately removed the kernel modules from any old 9.4 kernels but did give me a working 9.5 installation. I should note that I'm using ZFS 2.2.6, while you're using 2.1.15. Version 2.1.16 is currently being prepared. The notes say that the 9.5 kernel broke the build. Take a look at #16781. You may need to apply the patches shown there or move to 2.2.6. I think 2.2 is stable now. If you're concerned, don't do a feature upgrade. But we've been running with 2.2.6 with zpool upgrade done in production on a variety of systems with no trouble. BRT is still not on by default. |
Yes I’m running stable, and a package reinstall didn’t solve the issue. Depending on how the PR progresses I might switch to testing instead. |
I'm seeing the same problems with ZFS ABI on AlmaLinux 9.5. All updates are done with dnf. On separate Alma 9.5 system, zfs is okay. On the 2nd system I'm holding off dnf updates until this is resolved. |
System information
Describe the problem you're observing
Following the docs doesn't produce a usable ZFS install
Describe how to reproduce the problem
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: