<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<br>Hi All:<br><br>I am hitting a strange behavior during truck replication (so far it has occurred to one machine out of 10). I have two machines node1 and node2, and I am restoring metadata on node2. Whenever I do the following (as mentioned on truck replication page) resynchronization takes place. Any idea what could be causing this, any clues to debug such issues? <br><br>drbdsetup 1 new-current-uuid --clear-bitmap<br>drbdadm detach res<br>drbdmeta_cmd=$(drbdadm -d dump-md res)<br>drbdadm detach res <br>${drbdmeta_cmd/dump-md/restore-md} /var/testmeta<br><br><br>dmesg output:<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>block drbd1: conn( Unconnected -> WFConnection ) <br>block drbd1: Handshake successful: Agreed network protocol version 91<br>block drbd1: conn( WFConnection -> WFReportParams ) <br>block drbd1: Starting asender thread (from drbd1_receiver [24837])<br>block drbd1: data-integrity-alg: <not-used><br>block drbd1: drbd_sync_handshake:<br>block drbd1: self C48D0F6F05011D66:02D67DD221F19CD8:0000000000000004:0000000000000000 bits:669554939 flags:0<br>block drbd1: peer C48D0F6F05011D66:02D67DD221F19CD8:0000000000000004:0000000000000000 bits:0 flags:0<br>block drbd1: uuid_compare()=0 by rule 40<br>block drbd1: No resync, but 669554939 bits in bitmap!<br>block drbd1: peer( Unknown -> Secondary ) conn( WFReportParams -> Connected ) pdsk( DUnknown -> Inconsistent ) <br>block drbd1: peer( Secondary -> Primary ) pdsk( Inconsistent -> UpToDate ) <br>block drbd1: drbd_sync_handshake:<br>block drbd1: self C48D0F6F05011D66:02D67DD221F19CD8:0000000000000004:0000000000000000 bits:669554939 flags:0<br>block drbd1: peer 40BD0C3BDCF22CB9:C48D0F6F05011D66:0000000000000004:0000000000000000 bits:0 flags:0<br>block drbd1: uuid_compare()=-1 by rule 50<br>block drbd1: Becoming sync target due to disk states.<br>block drbd1: conn( Connected -> WFBitMapT ) <br>block drbd1: conn( WFBitMapT -> WFSyncUUID ) <br>block drbd1: helper command: /sbin/drbdadm before-resync-target minor-1<br>block drbd1: helper command: /sbin/drbdadm before-resync-target minor-1 exit code 0 (0x0)<br>block drbd1: conn( WFSyncUUID -> SyncTarget ) <br>block drbd1: Began resync as SyncTarget (will sync 2678219756 KB [669554939 bits set]).<br><br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>version: 8.3.4 (api:88/proto:86-91)<br>GIT-hash: 70a645ae080411c87b4482a135847d69dc90a6a2 build by rmake-chroot@localhost.localdomain, 2009-10-27 15:57:44<br><br> 1: cs:SyncTarget ro:Secondary/Primary ds:Inconsistent/UpToDate C r----<br> ns:0 nr:9735808 dw:9731552 dr:0 al:0 bm:592 lo:135 pe:29068 ua:133 ap:0 ep:1 wo:b oos:2668488204<br> [>....................] sync'ed: 0.4% (2605944/2615448)M<br> finish: 62:56:09 speed: 11,768 (11,460) K/sec<br><br><br><hr id="stopSpelling">From: tech_j@hotmail.com<br>To: lars.ellenberg@linbit.com; drbd-user@lists.linbit.com<br>Date: Mon, 2 Nov 2009 19:29:01 +0000<br>Subject: Re: [DRBD-user] Truck replication<br><br>
<style>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Verdana;}
</style>
Thats correct. The problem was with my perception of how it suppose to work versus the actual behavior. Truck based replication worked perfectly for me. After initial UpToDate/UpToDate message I untared the my directory structure on drbd mounted device and monitored dw (disk write) status from which I was able to see disk writes happening. Before this I was hoping to see UpToDate/Inconsistent(or Outdated) ds message, but that was just my perception.<br><br>Thanks a lot for help.<br><br>Regards,<br>Jay<br><br><br>> Date: Sat, 31 Oct 2009 10:17:22 +0100<br>> From: lars.ellenberg@linbit.com<br>> To: drbd-user@lists.linbit.com<br>> Subject: Re: [DRBD-user] Truck replication<br>> <br>> On Thu, Oct 29, 2009 at 07:41:16PM +0000, jay b wrote:<br>> > <br>> > Hi All:<br>> > <br>> > I am stuck with truck based replication. I have the following setup:<br>> > <br>> > node1 (primary):<br>> > /dev/sda7 [4TB]<br>> > /dev/drbd1<br>> > I have also created filesystem ext3 on drbd1<br>> > <br>> > node2:<br>> > <same configuration as above, but there is NO filesystem><br>> > <br>> > I am basically trying to avoid the initial sync time (if possible).<br>> > So, now node1 is primary and if I follow steps written on this page<br>> > http://www.drbd.org/users-guide/s-using-truck-based-replication.html<br>> > I can get both servers to display uptodate/uptodate state.<br>> > <br>> > But, when I mount /dev/drbd1 to /mnt/drbd (on node1 which is primary),<br>> > and copy files to /mnt/drbd, I do not see Uptodate/Inconsistent<br>> > message (via cat /proc/drbd on node1)<br>> <br>> Why would you expect node2 to become "Inconsistent"<br>> during normal operation?<br>> <br>> > At this point I would assume that node2 should get some data and try<br>> > to sync with primary. Am I missing any steps?<br>> <br>> When you _connect_ the second node,<br>> it will do some (bitmap based) resync.<br>> <br>> Once connected, and "Connected Uptodate",<br>> it will do _online replication_.<br>> <br>> If there is problem, I don't see it?<br>> Either you or me or DRBD misunderstood something, I guess.<br>> <br>> -- <br>> : Lars Ellenberg<br>> : LINBIT | Your Way to High Availability<br>> : DRBD/HA support and consulting http://www.linbit.com<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>> drbd-user@lists.linbit.com<br>> http://lists.linbit.com/mailman/listinfo/drbd-user<br> <br><hr>Save up to 84% on Windows 7 until Jan 3-eligible CDN College or University students only. <a href="http://go.microsoft.com/?linkid=9691631">Hurry-buy it now for $39.99!</a> <br /><hr />Get a great deal on Windows 7 and see how it works the way you want. <a href='http://go.microsoft.com/?linkid=9691812' target='_new'>Check out the offers on Windows 7now.</a></body>
</html>