logo       

Re: What versions of the linux, cluster, dm and lvm2 tend to work well togt: msg#00099

linux.redhat.cluster

Subject: Re: What versions of the linux, cluster, dm and lvm2 tend to work well togther???

CAugustine@xxxxxxxxxxxxxxxxxxx wrote:
>
> Hi Everyone,
>
> I am running with the 2.6.10-1.770_FC3CRAW.root linux kernel,
> which I built it to support raw devices.
>
> I downloaded the CVS sources for RHEL4 branch of the cluster
> and the LVM2, and the device-mapper sources are from the HEAD
> of the CVS tree. I built and installed them on both of my linux systems.
>
> After rebooting:
>
> The ccsd command is executed successfully on both nodes.
> The "cman_tool join" command executed on both nodes eventually
> shows the msg: Cluster is quorate. Allowing connections.
>
> However, looking at the /proc/cluster/nodes files on both systems,
> I see the following:
>
> Node Votes Exp Sts Name
> 1 1 1 M ovn01
>
> Node Votes Exp Sts Name
> 2 1 1 M ovn02
>
> Why on ovn02 node, Node=2 and on ovn01 Node=1?
> Has each node created a cluster on its own? Some sort of brain split???

Yep that's a split brain. If expected_votes was set (correctly) to 2
then you wouldn't have quorum. /never/ set expected_votes to 1 on a real
system. "cman_tool join" will set it to the total number of nodes in
ccsd so check you have the same custer.conf file on both nodes.

I worry that your syslog still names the host "localhost", that might
easily be a network misconfiguration which would cause nodes not to be
able to see each other.

> Then, I ran "fence_tool join" successfully on both systems.
> However, the "clvmd" cmd gave me the following messages on
> both systems:
>
> Apr 20 10:06:09 localhost clvmd: Unable to create lockspace for
> CLVM: Inappropriate ioctl
> for device

Are you sure this is up-to-date ? creating a lockspace hasn't been an
ioctl operation for months now.
--

patrick



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise