Replies: 2 comments 1 reply
-
https://github.com/zeet-cc/zfs-rpms/blob/main/kernel-zfs.spec - I'm using this as a safeguard. It's an empty package that locks in |
Beta Was this translation helpful? Give feedback.
1 reply
-
I usually use this oneliner before rebooting after a zfs upgrade to check whether all kernels have zfs module:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
I run a single RHEL 9 server (Rocky, to be precise) for a small business. We used to run Fedora, but found it too fast moving, and almost every
dnf update
would end up breakingzfs
due to version incompatibility. Moving to Rocky/RHEL obviously helped matters a lot as it's much slower moving, and we'd largely been runningdnf update
fairly often expecting that we'd only be receiving security updates. This seemed to be fine, nothing ever changed to the point thatzfs
would stop being available after a reboot.Then, of course, this morning we upgraded, rebooted, and found
zfs
no longer working. A workaround in that ticket (dnf update --enablerepo=zfs-testing zfs
) got us running again.Is there some way we can ensure that we don't perform an update if the resulting system won't have working
zfs
? I was less vigilantly watchingdnf update
as I wasn't expecting azfs
breakage, but if there was any kind of warning/error, it apparently passed by unnoticed. We really only rundnf update
for security patches.Beta Was this translation helpful? Give feedback.
All reactions