<html xmlns:v="urn:schemas-microsoft-com:vml" 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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=SL link=blue vlink=purple><div class=WordSection1><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US>Hi,<br><br>> Either return as quickly as possible,<br>> or do not return at all.<br>><br>> Either way, don't call back into DRBD kernel code<br>> from inside a synchronously running handler.<br><br>Nowhere does it state that DRBD will detach automatically in all cases, but only if ‘detach’ strategy is set. Furthermore, the manual states:<br><br>“It is entirely left to the administrator’s discretion to implement I/O error handling using the command (or script) invoked by local-io-error.”<br><br>Nowhere does it say, don’t detach manually or call DRBD kernel code…<br>If I want to implement I/O error handling in the way: notify me and detach (not necessarily in this order), how would I proceed?<br><span style='color:#1F497D'><br></span>> It won't be "a bit out of sync".<br>><br>> It will be *inconsistent*.<br>> That's a polite word for "corrupt by design".<br><span style='color:#1F497D'><br></span>Doesn’t DRBD preserve write order? So if one node is Ahead and the other Behind, it’s behind but consistent (outdated as stated in the docs)?<br>As I’ve said, our write load is low enough that Ahead/Behind does not happen too often and if the state is Connected, then it is not too far behind (besides what is left in the network buffers and/or not yet hit secondary disk due to protocol A)?<span style='color:#1F497D'><br></span><span style='color:#1F497D'><br></span>Regards,<br>Saso Slavicic<span style='color:#1F497D'><br><br></span><o:p></o:p></span></p></div></body></html>