I have drbd set up to replicate data between two servers. One of these servers unfortunately kernel panic'd and rebooted. After coming back online, the server wants to do a full sync. It is the secondary server.<div><br>
</div><div>This is a bit difficult, as the the primary server is on the other side of the continent. We're using local cable providers for internet access, so speed is also an issue. There is about 750 GB of data that needs synced, and at our current speeds, that would take about a month (for the initial sync we had the two servers in the same location, so this wasn't an issue).</div>
<div><br></div><div>I'm wondering if there's anything we can do to get drbd to recognize the data that is currently on the server that is out of date. I found someone who had a similar issue, where after reboot drbd wanted to resync the entire system, but it seems unrelated since it had to do with no initial sync.</div>
<div><br></div><div>The following is the log from the secondary machine, around the point that "full sync required" is noted. Any help would be appreciated!</div><div><br></div><div>Thanks,</div><div>Richard</div>
<div><br></div><div><div>/var/log/messages.2:Jan 16 11:46:44 gilroy kernel: block drbd0: Starting worker thread (from cqueue/0 [95])</div><div>/var/log/messages.2:Jan 16 11:46:44 gilroy kernel: block drbd0: disk( Diskless -> Attaching )</div>
<div>/var/log/messages.2:Jan 16 11:46:44 gilroy kernel: block drbd0: Found 6 transactions (276 active extents) in activity log.</div><div>/var/log/messages.2:Jan 16 11:46:44 gilroy kernel: block drbd0: Method to ensure write ordering: barrier</div>
<div>/var/log/messages.2:Jan 16 11:46:44 gilroy kernel: block drbd0: max_segment_size ( = BIO size ) = 32768</div><div>/var/log/messages.2:Jan 16 11:46:44 gilroy kernel: block drbd0: drbd_bm_resize called with capacity == 1499974224</div>
<div>/var/log/messages.2:Jan 16 11:46:44 gilroy kernel: block drbd0: resync bitmap: bits=187496778 words=5859276</div><div>/var/log/messages.2:Jan 16 11:46:44 gilroy kernel: block drbd0: size = 715 GB (749987112 KB)</div>
<div>/var/log/messages.2:Jan 16 11:46:45 gilroy kernel: block drbd0: recounting of set bits took additional 70 jiffies</div><div>/var/log/messages.2:Jan 16 11:46:45 gilroy kernel: block drbd0: 224 KB (56 bits) marked out-of-sync by on disk bit-map.</div>
<div>/var/log/messages.2:Jan 16 11:46:45 gilroy kernel: block drbd0: disk( Attaching -> Inconsistent )</div><div>/var/log/messages.2:Jan 16 11:46:45 gilroy kernel: block drbd0: Barriers not supported on meta data device - disabling</div>
<div>/var/log/messages.2:Jan 16 11:46:45 gilroy kernel: block drbd0: conn( StandAlone -> Unconnected )</div><div>/var/log/messages.2:Jan 16 11:46:45 gilroy kernel: block drbd0: Starting receiver thread (from drbd0_worker [2867])</div>
<div>/var/log/messages.2:Jan 16 11:46:45 gilroy kernel: block drbd0: receiver (re)started</div><div>/var/log/messages.2:Jan 16 11:46:45 gilroy kernel: block drbd0: conn( Unconnected -> WFConnection )</div><div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: Handshake successful: Agreed network protocol version 94</div>
<div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: conn( WFConnection -> WFReportParams )</div><div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: Starting asender thread (from drbd0_receiver [2902])</div>
<div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: data-integrity-alg: <not-used></div><div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: drbd_sync_handshake:</div><div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: self 704EEF7DCB91803C:0000000000000000:E16701DDDCBB997C:F572CBCF520DFB48 bits:56 flags:0</div>
<div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: peer D7B6E3DCB6C68EBD:36357CED276F2437:E16701DDDCBB997D:F572CBCF520DFB48 bits:265245 flags:2</div><div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: uuid_compare()=-100 by rule 100</div>
<div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: Becoming sync target due to disk states.</div><div>/var/log/messages.2:Jan 16 11:46:57 gilroy kernel: block drbd0: Writing the whole bitmap, full sync required after drbd_sync_handshake.</div>
<div>/var/log/messages.2:Jan 16 11:46:59 gilroy kernel: block drbd0: 715 GB (187496778 bits) marked out-of-sync by on disk bit-map.</div><div>/var/log/messages.2:Jan 16 11:46:59 gilroy kernel: block drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) pdsk( DUnknown -> UpToDate )</div>
<div>/var/log/messages.2:Jan 16 11:59:40 gilroy kernel: block drbd0: conn( WFBitMapT -> WFSyncUUID )</div><div>/var/log/messages.2:Jan 16 11:59:41 gilroy kernel: block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0</div>
<div>/var/log/messages.2:Jan 16 11:59:41 gilroy kernel: block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0)</div><div>/var/log/messages.2:Jan 16 11:59:41 gilroy kernel: block drbd0: conn( WFSyncUUID -> SyncTarget )</div>
<div>/var/log/messages.2:Jan 16 11:59:41 gilroy kernel: block drbd0: Began resync as SyncTarget (will sync 749987112 KB [187496778 bits set]).</div><div>/var/log/messages.2:Jan 16 11:59:42 gilroy kernel: block drbd0: write: error=-95 s=71400s</div>
<div>/var/log/messages.2:Jan 16 11:59:42 gilroy kernel: block drbd0: Method to ensure write ordering: flush</div></div><div><br></div>