On Thu, Aug 09, 2007 at 12:13:09PM +0200, Pierguido wrote:
> Lars Ellenberg wrote:
> >you could configure some "auto-recovery strategies", see after-sb-#pri
> >settings in drbd.conf.
> Ok...i'll give a look
>>> >to get them reconnected and resynchronized manually,
> >you'd have to typically
> > chose one side to do
> > umount
> > drbdadm -- --discard-my-data connect XY
> > and maybe on the other side do normal
> > drbdadm connect XY
> Ok.
> Es: i have two hosts (host1 and host2) and one is down (host2), so in
> the meanwhile somethings is written in host1.
>> to resyncronize the host2 i have to go to host1 and do those
> commands....right?
sometimes it helps to read out loud the commands to be issued...
if you go to host1, and say "discard-my-data", "my" is host1.
you just told host1 to discard its data,
retransmitting any differences from host2.
given your description above, this is probably not what you meant.
> >we are going to make this less annoying than it is now by introducing a
> >write_quorum and IO-freeze on disconnect, then we can timeout for a
> >possible imminent reconnect (network hiccup only), and after that
> >timeout arbitrate (triggered by the cluster manager) which side may
> >continue, and which has to be fenced (or let it self-fence...).
> >
> >but for the time being, yes, I know, two-primaries is still "inconvenient"
> >when you have a flaky network.
> Actually i connect them using a crossover cable ;-)
> But i wanted to test all the possibilities :-)
--
: Lars Ellenberg Tel +43-1-8178292-0 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe http://www.linbit.com :
__
please use the "List-Reply" function of your email client.