<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF"><div><div class="gmail-h5"><br></div></div>>>I think this document might help:<br>>><a class="gmail-m_9042420997677087294moz-txt-link-freetext" href="https://www.drbd.org/en/doc/users-guide-83/s-initial-full-sync" target="_blank">https://www.drbd.org/en/doc/<wbr>users-guide-83/s-initial-full-<wbr>sync</a><br>
<br>>>or specifically, this command:<br>
<pre class="gmail-m_9042420997677087294screen"><b class="gmail-m_9042420997677087294userinput"><code>>>drbdadm -- --overwrite-data-of-peer primary <i class="gmail-m_9042420997677087294replaceable"><code>resource</code></i></code></b></pre></div></blockquote><div><br></div><div>I think that will work only for the initial sync and not in this case that data/metadata already exists on the secondary.</div><div><br></div><div>I believe the correct approach is to use the 'invalidate' option on the secondary node:<br></div><div><br></div><div><a href="http://www.drbd.org/en/doc/users-guide-83/re-drbdadm">http://www.drbd.org/en/doc/users-guide-83/re-drbdadm</a><br></div><div><br></div><div><div>"invalidate</div><div>Forces DRBD to consider the data on the local backing storage device as out-of-sync. Therefore DRBD will copy each and every block from its peer, to bring the local storage device back in sync."</div></div><div><br></div><div>Y.</div></div></div></div>