<div dir="ltr">Dear Phil,<br><br>We are verifying your patch for CASE-17;<div><br> - <a href="http://git.drbd.org/drbd-9.0.git/commitdiff/db0534012b16cb6708aeb57b8cca29816c4e5b52">http://git.drbd.org/drbd-9.0.git/commitdiff/db0534012b16cb6708aeb57b8cca29816c4e5b52</a><br><br>It's good for resolution of "sync progress percentage unchanged at 100.00.".<br>But another problem occurred.<br><br><br>1. Test Env.<br><br> - Version: lasted [86e4439]<br> - 2 nodes (drbd.conf sets for multi node, but we test just 2 nodes)<br> - protocol A; sndbuf-size 10M;on-congestion pull-ahead;congestion-fill 5M;<br><br><br>2. Test-steps<br><br> 1) make primary/secondary<br> 2) copy big file<br> 3) drbdadm disconnect at the beginning of copying<br> 4) drbdadm connect r0<br> 5) sometimes, UpToDate/UpToDate without resync despite of OOS remaining.<br><br><br>3. primary status<br><br>[root@drbd9-01 바탕화면]# drbdsetup status --verbose --statistics<br>r0 node-id:0 role:Primary suspended:no<br> write-ordering:flush<br> volume:0 minor:1 disk:UpToDate<br> size:4998328 read:6662461 written:3878932 al-writes:250 bm-writes:0<br> upper-pending:0 lower-pending:0 al-suspended:no blocked:no<br> drbd9-02 node-id:1 connection:Connected role:Secondary congested:no<br> volume:0 replication:Established peer-disk:UpToDate<br> resync-suspended:no<br> received:0 sent:6661324 out-of-sync:1931560 pending:0 unacked:0<br><br><br>4. Log<br> - primary log : </div><div> - <a href="http://pastebin.com/LKt0bmR5">http://pastebin.com/LKt0bmR5</a></div><div><br> - Please check my comments in the attached log files.<br><br><br>5. Quesstions<br><br> 1) Why does the resync stop despite of OOS remaining?</div><div><br></div><div> 2) Sometimes, AHEAD mode continues, why?</div><div><br> 3) On Windows DRBD, sometimes the following messages occur. Linux as well, I think.<br><br>Mon Apr 4 19:15:05.555 2016 (UTC + 9:00): <br>Mon Apr 4 19:15:32.595 2016 (UTC + 9:00): WDRBD_INFO: [receive_state] drbd r0/0 drbd2 2008r2-x64-pas1: SyncSource still sees bits set!! FIXME<br>Mon Apr 4 19:15:32.595 2016 (UTC + 9:00): <br>Mon Apr 4 19:15:32.612 2016 (UTC + 9:00): WDRBD_INFO: [drbd_resync_finished] drbd r0/0 drbd2 2008r2-x64-pas1: Resync done (total 34 sec; paused 0 sec; 52524 K/sec)<br>Mon Apr 4 19:15:32.612 2016 (UTC + 9:00): <br>Mon Apr 4 19:15:32.626 2016 (UTC + 9:00): _WIN32_v9_CHECK: n_oos=396551 rs_failed=0. Ignore assert <br><br><br> 3-1) On receive_state(), Is "FIXME" no problem?</div><div><br> /* TODO: Since DRBD9 we experience that SyncSource still </div><div> has bits set... NEED TO UNDERSTAND AND FIX! */</div><div> drbd_warn(peer_device, "SyncSource still sees bits set!! FIXME\n");<br><br><br> 3-2) On drbd_resync_finished(), Why does this ASSERT occure?</div><div><br> D_ASSERT(peer_device, (n_oos - peer_device->rs_failed) == 0);<br><br><br>Thanks.</div><div><br></div><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div></div></div></div></div></div></div>
</div></div>