[Pacemaker] Problem with drbd 2 primary + OCFS2 + server

Dejan Muhamedagic dejanmm at fastmail.fm
Thu Aug 20 10:30:36 EDT 2009


On Wed, Aug 19, 2009 at 07:51:58PM +0200, cudak at sonet.internetdsl.pl wrote:
> hj lee pisze:
>> I found two issues in your configuration.
>> 1. Still the last location constraint does not make sense. The server-www 
>> is a group, not multistate master/slave, so role=master is wrong. This 
>> should be msDRBD.
>> 2. Why did you set max-master=2? As you said, both nodes came up as 
>> master, most of constraints you configured does not make sense. For 
>> example, colocation constraints says that server-www must be run with DRBD 
>> master. But there are two masters in your cluster, it can not run it. Try 
>> it again by deleting max-master=2, the default is 1.
>> Thanks
> Is it master-max means: "how many copies of the resource can be promoted to 
> master status" ( by Configuration_Explained.pdf  from clusterlabs.org)? 
> Whena I'm changeing  role in location to role=master crm it shows: "Bad 
> role specified... "

You should use "Master".

> In addition to not starting filesystem, I've change param start-delay from 
> default value to 60 of primitive resOCFS2 and now all filesystem are 
> mounted properly.

Eh? How did that help? In that case there are definitely problems
with some resource agent.

BTW, as far as I know, the ocf:heartbeat:drbd RA doesn't support
multimaster configurations. Perhaps the new ocf:linbit:drbd does.
Best to ask on some drbd forum.



> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker

More information about the Pacemaker mailing list