[DRBD-user] changing clock time and sync

[Helmut Wollmersdorfer]

Today I changed the time of my primary node from 05:44 to the correct 06:44
UTC, which should be nearly the same as on the secondary. I did this by a
reboot of the primary only and changed the time in BIOS.

Here the part of syslog on the secondary:
Mar 22 06:45:57 via2 kernel: drbd0: Connection lost.
Mar 22 06:47:53 via2 kernel: drbd0: Connection established. size=2980 KB /
blksi
ze=4096 B
Mar 22 06:47:53 via2 kernel: drbd0: Synchronisation started blks=64

Now it seems to sync forever:
root at via2:~# date
Mo Mär 22 10:27:32 UTC 2004
root at via2:~# cat /proc/drbd
version: 0.6.10 (api:64/proto:62)

0: cs:SyncingQuick st:Primary/Secondary ns:0 nr:0 dw:0 dr:0 pe:0 ua:0

This seems to be very long for 3 GB and a 100 Mbit direct link. 
Did I hit a curious testcase?

This is my (untuned) drbd.conf:
resource drbd0 {
  protocol = C
  fsckcmd  = fsck -p -y

  disk {
    do-panic
    disk-size = 2980k
  }
  net {
     sndbuf-size = 512k
     sync-nice  = -18
  }
  on via1 {
    device  = /dev/nb0
    disk    = /dev/hdc1
    address = 10.0.10.10
    port    = 7788
  }

  on via2 {
    device  = /dev/nb0
    disk    = /dev/hdc1
    address = 10.0.10.11
    port    = 7788
  }
}

Helmut Wollmersdorfer

-- 
+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz