Hi,<br>
When does the drbd at both machines decide to sync?<br>
Is it always syncing in background?<br>
Does it sync on change of metadisk?<br>
Does it sync when a shift of state occurs? Secondary->Primary etc. <br>
<br>
I read about the DRBD+ for more than two nodes operaiton, is it open source, free to use?<br>
<br>
Usman <br>
<br><div><span class="gmail_quote">On 9/18/06, <b class="gmail_sendername">Milind Dumbare</b> <<a href="mailto:milind@linsyssoft.com">milind@linsyssoft.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, 2006-09-18 at 15:21 +0200, Usman Ahmad wrote:<br>> Hi,<br>><br>> Thanx for the explanation. Just curious what "halt -f" does? related<br>> to DRBD or is it a system command?<br>><br>its halt command, nothing to do with DRBD.
<br><br>> Regards<br>> Usman<br>><br>> On 9/16/06, Tim Jackson <<a href="mailto:lists@timj.co.uk">lists@timj.co.uk</a>> wrote:<br>> Usman Ahmad wrote:<br>><br>> Hi, it would be easier if you didn't top-post. Thanks.
<br>><br>> > No, there is no firewall setup, but same question again, it<br>> may be<br>> > stupid. How long does a drbd node wait for changing the<br>> other node to<br>
> > unknown state ( i guess this is done through different<br>> timeout<br>> > parameters etc.), and if the other server comes back up<br>> again, is it<br>> > changed normally or not?
<br>><br>> First, just in case it wasn't clear, DRBD doesn't change the<br>> status of<br>> the *local* node; only an external program (e.g. Heartbeat)<br>> does that.<br>> As for what it shows for the status of the *remote* node,
<br>> well, I<br>> haven't read the code but it normally seems to me to be pretty<br>> fast.<br>> Again, read the logs: if the local node is primary (and writes<br>> are
<br>> taking place, I think), then you should start seeing "ko"<br>> warnings<br>> quickly, and how long before the other node is declared dead<br>> depends on<br>> the "ko-count" configuration option. You will see all kinds of
<br>> warnings<br>> from DRBD when the nodes can't communicate. See also my bug<br>> report on<br>> this list the other day though, about DRBD not reporting a<br>> transition of
<br>> the remote node to "Unknown" status in the logs.<br>><br>> > on-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep<br>> 60 ; halt -f";<br>> > halt -f?
<br>><br>> That's not directly related. This is what happens if the<br>> machine is<br>> inconsistent and the cluster is degraded when DRBD starts<br>> (i.e. the<br>> machine should be becoming primary, but it doesn't have a full
<br>> copy of<br>> the data).<br>><br>> Tim<br>> _______________________________________________<br>> drbd-user mailing list<br>> <a href="mailto:drbd-user@lists.linbit.com">
drbd-user@lists.linbit.com</a><br>> <a href="http://lists.linbit.com/mailman/listinfo/drbd-user">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>><br>><br>><br>> --<br>> Usman Ahmad Malik
<br>> _______________________________________________<br>> drbd-user mailing list<br>> <a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>> <a href="http://lists.linbit.com/mailman/listinfo/drbd-user">
http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>--<br>"The world is divided into one group: those who start counting at 0,<br>and those who don't."<br><br></blockquote></div><br><br clear="all"><br>--
<br>Usman Ahmad Malik