Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I encounter the same problem . Fortunately,I have solved it. Format the sharedisk on each node. Until each node can read same file on sharedisk. Then setup the Quorum , it worked. I think this solution is not exactly correct,just solve the problem.
Originally posted by vamosb What partition should I format? On the shared disk there are two partition for two raw device. I think I do not need to format them.
You should format the raw device as ext3,and make a file for read by each node to ensure share disk worked.
I have a similar problem, in this case we cant see the nodes active at the same time:
Clustat second node:
Cluster Status - cluster 10:26:58
Incarnation #1
(This member is not part of the cluster quorum)
Member Status
------------------ ----------
172.16.0.49 Active <-- You are here
172.16.0.48 Inactive
No Quorum - Service States Unknown
clustat first node
Cluster Status - cluster 10:26:42
Cluster Quorum Incarnation #1
Shared State: Shared Raw Device Driver v1.2
Member Status
------------------ ----------
172.16.0.49 Inactive
172.16.0.48 Active <-- You are here
Service Status Owner (Last) Last Transition Chk Restarts
-------------- -------- ---------------- --------------- --- --------
second node:
[root]# service clumanager status
Se está ejecutando clumembd (pid 2673)...
Se está ejecutando cluquorumd (pid 2671)...
Se está ejecutando clulockd (pid 2678)...
clusvcmgrd está parado
Note: Service manager is not running because this member
is not participating in the cluster quorum.
first node
[root]# service clumanager status
Se está ejecutando clumembd (pid 5547)...
Se está ejecutando cluquorumd (pid 5545)...
Se está ejecutando clulockd (pid 5552)...
Se está ejecutando clusvcmgrd (pid 5577)...
The RedHat cluster suite needs more than 50% of members to start quorum.
If you use Disk Tiebreaker, this resouce give one more point to cluster, but is not recommended to cluster with 2 members.
If you have a network problem, you need to give one more point to cluster using "cluforce member_name"
see: man cluforce
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.