Hi,

On Thu, Aug 12, 2010 at 04:28:24PM +0200, Alain.Moulle wrote:
> Hi Dejan ,
> 
> pacemaker-1.1.2-2

That sounds like quite recent. There was an important patch at
the end of May. What does "/usr/lib/heartbeat/crmd version" say?

> ok, but in later versions, it will work as I would like ? meaning that
> all clone-fs will be started on both sides whatever the node where the
> group is active ?

Try the constraints suggested below. They should be equivalent to
resource sets. Actually, the second version ...

> Thanks for precision.
> Alain
> 
> > Which version do you run? If it's not a recent post 1.1.2, then
> > clones don't work well with resource sets. Instead you can chain
> > constraints:
> >
> > order o1 inf: a b
> > order o2 inf: b c
> >
> > But, I guess that fs1 and fs2 are independent, right? If so, then
> > it should be:
> >
> > order o1 inf: fs1 g1
> > order o2 inf: fs2 g1

... here, should have the same effect like:

order o inf: ( fs1 fs2 ) g1

The parentheses mean that the two fs resources can be started in
parallel.

But I'm not sure how should the clone be treated if collocated
with another resource, i.e. if there is going to be an instance
started on nodes where that resource doesn't run. Note also that
the collocation with resource sets is inverted when compared to
the two-resource collocation:

collocation c1 inf: g1 fs1
collocation c2 inf: g1 fs2

is

collocation c inf: ( fs1 fs2 ) g1

Well, perhaps that's the culprit in this case. Could you please
try that too.

Thanks,

Dejan

> >
> > Thanks,
> >
> > Dejan
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to