Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi.
Same error occurred at Windows DRBD.
After resync on congestion-mode, sometimes the resync progress percentage
is not change at 100.00.
1. Node A: status:
C:\Windows\System32>drbdadm status r0
r0 role:Primary
disk:UpToDate
W7X86-3 role:Secondary
replication:SyncSource peer-disk:Inconsistent done:100.00
2. Node B status:
C:\Windows\System32>drbdadm status r0
r0 role:Secondary
disk:UpToDate
W7X86-2 role:Primary
peer-disk:UpToDate
3. Logs
Let me attach full log files here:
- node A: http://pastebin.com/LF1FvZ44
- node B: http://pastebin.com/7nTcvt9x
Please see my comments in above log files.
I think the node A didn't receive the "resync done" signal(resync done
timer trigger?) at the end of resync.
Please check.
Thanks.
2016-02-14 19:33 GMT+09:00 김재헌 <jhkim at mantech.co.kr>:
> Hi,
>
> After resync, sometimes the resync progress percentage is not change at
> 100.00.
>
>
> 1. Version
> - V9.0.1-1
> - CentOS 7
>
>
> 2. Status
>
> 1) node1
>
> [root at drbd9-01 drbd.d]# drbdadm status r0
> r0 role:Primary
> disk:UpToDate
> drbd9-02 role:Secondary
> replication:SyncSource peer-disk:Inconsistent done:100.00
>
>
> 2) node2
>
> [root at drbd9-02 drbd.d]# drbdadm status r0
> r0 role:Secondary
> disk:UpToDate
> drbd9-01 role:Primary
> peer-disk:UpToDate
>
>
> 3. Temporary resolution
> - If we do disconnect and connect on node1, the node-1 becomes normal
> "UpToDate" status.
>
>
> Thanks.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160309/d3e6f7f4/attachment.htm>