<div dir="auto"><div><div class="gmail_extra"><div class="gmail_quote">On 11 Sep 2017 4:20 pm, "Ravi Kiran Chilakapati" <<a href="mailto:ravikiran.chilakapati@gmail.com">ravikiran.chilakapati@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thank you for the response Roland. <div><br></div><div>I will start going through the source code. In the meantime, it will be great if these preliminary questions can be answered. <div><br></div><div>Q: Is Protocol C a variant of any standard atomic commit protocol (like 2PC/3PC etc.)? Or is it a proprietary algorithm? </div><div>Q: Let's assume there are 2 disks (D1, D2). Let's assume that D2 is experiencing a fail-recover situation, but D1 has failed after a D2 failure, but before D2 has recovered. What is the behavior of DRBD in such a case? Are all future disk writes blocked until both D1 and D2 are available, and are confirmed to be in sync? </div></div></div></blockquote></div></div></div><div dir="auto">You need to explain what D1 and D2 exactly are. Are they 2 disks composing a single volume that is used as a baking device of a single drbd resource? Or maybe they are disks for a separate volumes of a single drbd resource? Or maybe each is a backing devices of 2 separate drbd resources? Or maybe ... etc.etc.etc.</div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><br></div><div>Regards,</div><div>Ravi.</div><div class="elided-text"><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 8, 2017 at 2:07 AM, Roland Kammerer <span dir="ltr"><<a href="mailto:roland.kammerer@linbit.com" target="_blank">roland.kammerer@linbit.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Thu, Sep 07, 2017 at 04:08:10PM -0700, Ravi Kiran Chilakapati wrote:<br>
> Hi,<br>
><br>
> I was wondering where I could find more information on DRBD's Protocol C? I<br>
> was hoping I could find a resource without resorting to the source code.<br>
><br>
> I tried the following with no luck.<br>
> 1) asking around on Stackoverflow (<br>
> <a href="https://stackoverflow.com/questions/45998076/an-explanation-of-drbd-protocol-c" rel="noreferrer" target="_blank">https://stackoverflow.com/ques<wbr>tions/45998076/an-explanation-<wbr>of-drbd-protocol-c</a><br>
> )<br>
> 2) scanning the user guide (<a href="http://docs.linbit.com/docs/users-guide-9.0/" rel="noreferrer" target="_blank">http://docs.linbit.com/docs/u<wbr>sers-guide-9.0/</a>)<br>
<br>
</span>There is no official "user-friendly" documentation besides the UG. So<br>
ask specific questions and we can answer them (and probably add them to<br>
the UG in some high level section) or read the code...<br>
<br>
Regards, rck<br>
______________________________<wbr>_________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">http://lists.linbit.com/mailma<wbr>n/listinfo/drbd-user</a><br>
</blockquote></div><br></div></div></div></div></div>
<br>______________________________<wbr>_________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">http://lists.linbit.com/<wbr>mailman/listinfo/drbd-user</a><br>
<br></blockquote></div><br></div></div></div>