<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body style="font-family: Courier New; font-size: 13px;"
bgcolor="#FFFFFF" text="#000000">
<div id="QCMcontainer" style="font-family:Courier
New;font-size:13px;">Sorry, I've missed the link:<br>
<a class="moz-txt-link-freetext" href="https://forum.proxmox.com/threads/kernel-panic-with-proxmox-4-1-13-drbd-9-0-0.26194/">https://forum.proxmox.com/threads/kernel-panic-with-proxmox-4-1-13-drbd-9-0-0.26194/</a><br>
<br>
<br>
<span style=" font-family:Courier New; font-size:14px;
font-weight:normal" class="headerSpan">
<div class="moz-cite-prefix">Il 11/04/2016 10:13, Claudio Nicora
ha scritto:<br>
</div>
</span>
<blockquote style="font-size: medium;"
cite="mid:570B5CC1.3060606@gmail.com" type="cite">Welcome
aboard, and thanks for bringing back an issue that nobody took
care of since now.
<br>
It means I was not the alone...
<br>
<br>
I've had the same issue a few months ago, I've reported it here
(and on Proxmox forums) but the issue is still there.
<br>
<br>
Linbit: nobody took care of it (however it's a kernel crash,
should be critical enough...)
<br>
Proxmox: a kernel with an updated DRBD module (still DRBD 9.0)
was released but the issue persisted. Still wondering how a
"non-production ready" feature could end up in a "production
ready" bundle like Proxmox 4 without a choice to get DRBD 8.4
back.
<br>
<br>
I've sorted it out by downgrading DRBD module to 8.4 and
building the kernel module + DRBD tools on my own.
<br>
This is the post on Proxmox forum with a backlink to my blog
post where I detailed the actions to downgrade the module.
<br>
I've also set up a script to run after each Proxmox kernel
upgrade, just in case.
<br>
<br>
PS: still waiting for a feedback from Linbit/Proxmox guys ;)
<br>
</blockquote>
<br>
</div>
</body>
</html>