Hi-<br><br>I'm experiencing a strange issue with DRBD not following protocol C and replication happening long after local writes are complete. If, for example, I've got /dev/drbd0 mounted at /mnt with an ext3 filesystem, `dd if=/dev/zero of=/mnt/test.zero bs=1000M count=1` will write the file at local speeds and complete long before DRBD replicates any of it (or as far as I can see by watching /proc/drbd) It sometime takes as long as 10s before there is any activity in /proc/drbd.<br>
<br>I've only observed this happening when I write to a file system on a DRBD resource or using a Xen VM dependent on DRBD (both phy: and file: configurations). If I write directly to the /dev/drbdXX device, /proc/drbd reports replication is taking place when it should and writes do note complete until after activity in /proc/drbd has stopped. <br>
<br>My aim is to map DRBD resources to LVs. I have done some testing using both LVs and physical partitions as DRBD resources' devices and have found the same results. I'm using 8.3.1 compiled against 2.6.27.21-0.1-xen on OpenSUSE 11.1. From what I can tell there must be something else on a higher level messing with replication but I can't for the life of me think of what it might be. I haven't seen anything out of the ordinary in log files. After data is finally replicated, files check out okay on the other node but this is not the behavior I was expecting. Attached is a copy of the most recent test drbd.conf. Thanks<br>
<br>Any assistance would be greatly appreciated, <br>CSMITH<br><br>global { usage-count no; }<br>resource test {<br> protocol C;<br> net { shared-secret "test"; }<br> syncer { rate 100M; }<br>
on node1 {<br> device /dev/drbd10;<br> disk /dev/sdb4;<br> address <a href="http://192.168.100.2:7795">192.168.100.2:7795</a>;<br> meta-disk internal;<br>
}<br> on node2 {<br> device /dev/drbd10;<br> disk /dev/sdb4;<br> address <a href="http://192.168.100.1:7795">192.168.100.1:7795</a>;<br> meta-disk internal;<br>
}<br>}<br><br>