<div>Hi Lars,</div>
<div> </div>
<div>I downloaded the trunk of 8.2 some weeks ago (GIT-hash: 61b7f4c2fc34fe3d2acf7be6bcc1fc2684708a7d) and created rpms. I assume it is 8.2.7.</div>
<div> </div>
<div>Unfortunatelly I have not yet tested such cases against 8.3.</div>
<div> </div>
<div>Thanks<br><br></div>
<div class="gmail_quote">2009/2/5 Lars Ellenberg <span dir="ltr"><<a href="mailto:lars.ellenberg@linbit.com">lars.ellenberg@linbit.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">On Thu, Feb 05, 2009 at 02:25:54PM +0000, Maros Timko wrote:<br>> Hi all,<br>><br>> we are running Xen VMs on top of DRBD, DRBD resources are defined on top of<br>> LVMs. We use 64-bit CentOS 5.2 (2.6.18-92.1.22.el5xen). Previously we were<br>
> testing the setup with DRBD RPMs from CentOS distribution (8.2.6-3), but we<br>> met an issue: device on top of which still runs Xen VM at the time of DRBD<br>> communication path is broken (we just removed dedicated crossover cable for<br>
> simple tests) for some time, stalled at the sync progress at 100% after<br>> reconnection. This was easily reproducible and the more changes occured on<br>> the device when disconnected the higher probability of the stalling. We use<br>
> synchronuous resync definition (using "after" config) so it means for us<br>> that all the followers are stuck in PausedSync states with inconsistent data<br>> state. Reconnection of this device solves the issue, however, there is no<br>
> handler for such situations and devices itself looks happy (syncing although<br>> at 100%).<br>><br>> So we tried to upgrade to DRBD 8.2.7 (GIT-hash:<br>> 61b7f4c2fc34fe3d2acf7be6bcc1fc2684708a7d) - it seemed like this release<br>
> solved such issue. However, we still experience this, although not so often<br>> and the behaviour is different - device get stalled at e.g. 25% and then the<br>> number decreases. This is I think because still new changes are coming so<br>
> the update of statistics gives such results.<br><br></div>likely something completely different than the issue described in the<br>first paragraph.<br>
<div class="Ih2E3d"><br>> I tried to look for stalling issues on the list but seems like there is no<br>> definite answer. If anyone has an experience with some kind of information<br>> on how to prevent such issues, it would be great. Most of the issues what I<br>
> saw were related to network quality or huge amount of data that needs to be<br>> resynced. But we are trying simply plug out the cable.<br>><br>> I am enclosing dump of related device only, all others are exactly the<br>
> same excepting LVMs ... and corresponding /var/log/messages section.<br><br></div>This:<br>
<div class="Ih2E3d"><br>> Feb 5 09:35:06 svdom0-0148 kernel: drbd1: cs:SyncSource rs_left=19637 > rs_total=19587 (rs_failed 0)<br><br></div>is an interessting message.<br>This should not normally happen,<br>though there are situations where it may happen.<br>
<br>Which one, exactly, is this, 8.2.7?<br><br>Did you try with 8.3.0?<br><br>--<br>: Lars Ellenberg<br>: LINBIT | Your Way to High Availability<br>: DRBD/HA support and consulting <a href="http://www.linbit.com/" target="_blank">http://www.linbit.com</a><br>
<br>DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.<br>__<br>please don't Cc me, but send to list -- I'm subscribed<br>_______________________________________________<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" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br></blockquote>
</div><br>