Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
All, I recieved some replies to this, but I think the question has been misunderstood. The backing device on the two machines were once componentns in a DRBD array. One of the machines (machine-2) was turned off and time passed (several weeks) so many changes occured on machine-1. DRBD's sync method is VERY slow and mostly stalling on my VPN link, it is estimated that it will take atleast 2 months for the 60GB of data to sync using DRBD's sync. I can sync it much faster using a method outside of drbd and making the backing device on both machines identical. DRBD doesn't seem to be aware of my manual sync and happily tries to continue its own sync. My question is: How can I tell DRBD that my "Inconsistent" component is really Consistent ? Roy Keene Planning Systems Inc On Tue, 13 Sep 2005, Roy Keene wrote: > All, > > Assuming I use "meta-data: internal" for both systems and both > systems are of the same CPU arch, can I start with an initial state of > synchronized if I manually mirror the backing device for my two DRBD mirror > components ? > > For example, if I have machine-1 and machine-2 and they each have /dev/sde1 > as their backing device (and using meta-data: internal), can I just do: > > root at machine-2# nc -l -p 5001 > /dev/sde1 < /dev/null > ... > root at machine-1# dd if=/dev/sde1 | nc machine-2 5001 < /dev/null > > and have DRBD operate correctly when started on both machines ? > > Roy Keene > Planning Systems Inc > ++++++++[->++++<]>[->+>++>+++>++++<<<<]>>++++++++++++++++.>++++++ > ++++++.-----------.+++++++++++++..-----.+++++.-------.<<.>+++.>>- > ------.------.+.<--.>-------.++++++.<<<.>----------.>>-----.<--.< > <<++++++++++. >