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
9.1.8 can't see metadata from earlier versions #45
Comments
Hi, thanks for the report. We have implemented a fix for this (d7d76aa) which will soon be released, likely within the next week. If you easily can (and if this is a non-production system), it would be great if you could build DRBD from that commit and verify that the fix resolves the issue for you. If not, the obvious workaround is to stay on 9.1.7 for now (or downgrade). |
Hi, ElRepo.org maintainer kindly provided testing packages with this patch applied: https://elrepo.org/bugs/view.php?id=1250 I'll try them today in a couple of test servers. |
Great, please let us know if the issue is fixed. By the way, we have also just released 9.1.9-rc.1 which also includes this patch: https://lists.linbit.com/pipermail/drbd-user/2022-August/026291.html |
No luck with elrepo.org provided packages:
dmesg output
|
Seems like something went wrong with the rebuild there. I suspect the kernel compatibility patch cache was not updated correctly. We have internally verified that this issue is fixed with >9.1.9. Please try with 9.1.10 and see if that works for you. |
Sorry for not replying before, I didn't have time to test it till right now. Version 9.1.10 seems to work fine with 9.1.7:
Thanks! |
Hi,
I have a couple of CentOS 7 servers which were using older drbd versions from elrepo.org (9.0.30) and after an update to 9.1.8 and a reboot, the resources stayed in Diskless status.
I see this in dmesg:
After downgrading to drbd 9.1.7 everithing went back to normal.
A few days later, the same happened with a pair of AlmaLinux 8 servers: 9.1.8 stays in Diskless mode, 9.1.7 and older work fine.
Those systems are otherwise fully uptodate.
The text was updated successfully, but these errors were encountered: