<html><head><style type="text/css"></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:10pt"><div style="font-family: times new roman,new york,times,serif; font-size: 10pt;">Thanks for the info. Yes I understand what you are saying. However, if <br>you do not specify and ip-tiebreaker I assumed it used the disk tiebreaker<br>by default.<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Lon Hohberger <lhh@redhat.com><br>To: linux clustering <linux-cluster@redhat.com><br>Sent: Monday, October 2, 2006 9:20:14 AM<br>Subject: Re: [Linux-cluster] How does disk prevent split brain?<br><br><div>On Sun, 2006-10-01 at 20:59 -0700, Rick Rodgers wrote:<br>> According to RH documentation and the engineers you can have a safe<br>> two node <br>> cluster without having to have an ip-tiebreaker. They say it will use<br>> the disk tie-breaker.<br>> <br>> How is this possible? Since clulockd is running separately on each of<br>> the nodes how does<br>> it prevent each node from accessing the disk at the same time and<br>> declaring himself the <br>> Active node? If it is through some sort of locking mechanism that<br>> insures this can you please<br>> be technically specific in what it is?<br><br>Only one will be the lock master, because there is knowledge that both<br>nodes are actually still online.<br><br>You can not disable/move services when the cluster network is dead, but<br>both nodes can continue running the services they already are running.<br>Most people should probably use the disk tiebreaker if they want<br>failover if a node's cluster network gets disconnected.<br><br>-- Lon<br><br><br>--<br>Linux-cluster mailing list<br>Linux-cluster@redhat.com<br><a target="_blank" href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a><br></div></div><br></div></div><br></body></html>