<div dir="ltr">Hi there,<div><br></div><div>In reading this page (<a href="http://www.drbd.org/users-guide-8.3/s-gi.html">http://www.drbd.org/users-guide-8.3/s-gi.html</a>) your online docs, in the "How DRBD uses generation identifiers" -> #5 "Current UUID matches peer's historical UUID" section, I found something a bit confusing and I'm suspicious that it may be incorrect.</div>
<div><br></div><div>It states:</div><div><br></div><div>"The local node detects that its current UUID matches one of the peer's historical UUID's. This implies that while the two data sets share a common ancestor, and the local node has the up-to-date data, the information kept in the local node's bitmap is outdated and not useable. Thus, a normal synchronization would be insufficient. DRBD now marks the entire device as out-of-sync and initiates a full background re-synchronization, with the local node becoming the synchronization source."</div>
<div><br></div><div>If the local node's current UUID matches one of the peer's historical UUIDs wouldn't that mean that the local node's data is an older generation than the peer's and the local node's data should be considered out-of-date and replaced with the peer node's data?</div>
<div><br></div><div>Also, thanks for providing and hosting these high quality docs! I hope that this discussion can serve to help make them even better or set me straight ;)</div><div><br></div><div>-- <br><div dir="ltr">
Jonathan Woodbury<div>Ganeti SRE - NYC<br></div><div>Google Inc.</div></div>
</div></div>