<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">We use the fence_kump* code extensively in production and have never had any problems with it (other than the normal initial configuration challenges). Kernel panic + kdump is our most common failure mode, so we exercise this code quite
a bit.<o:p></o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Chris<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Users <users-bounces@clusterlabs.org><br>
<b>Date: </b>Thursday, February 24, 2022 at 7:22 AM<br>
<b>To: </b>users@clusterlabs.org <users@clusterlabs.org><br>
<b>Subject: </b>[ClusterLabs] Q: fence_kdump and fence_kdump_send<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Hi!<br>
<br>
After reading about fence_kdump and fence_kdump_send I wonder:<br>
Does anybody use that in production?<br>
Having the networking and bonding in initrd does not sound like a good idea to me.<br>
Wouldn't it be easier to integrate that functionality into sbd?<br>
I mean: Let sbd wait for a "kdump-ed" message that initrd could send when kdump is complete.<br>
Basically that would be the same mechanism, but using storage instead of networking.<br>
<br>
If I get it right, the original fence_kdump would also introduce an extra fencing delay, and I wonder what happens with a hardware watchdog while a kdump is in progress...<br>
<br>
The background of all this is that our nodes kernel-panic, and support says the kdumps are all incomplete.<br>
The events are most likely:<br>
node1: panics (kdump)<br>
other_node: seens node1 had failed and fences it (via sbd).<br>
<br>
However sbd fencing wont work while kdump is executing (IMHO)<br>
<br>
So what happens most likely is that the watchdog terminates the kdump.<br>
In that case all the mess with fence_kdump won't help, right?<br>
<br>
Regards,<br>
Ulrich<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users">https://lists.clusterlabs.org/mailman/listinfo/users</a>
<br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/">https://www.clusterlabs.org/</a>
<o:p></o:p></p>
</div>
</div>
</body>
</html>