Hi , I have a ocfs2 FS that I have declared as a clone resource: clone-fs, and I want both res1 and res2 to be "groupped" (group-res) and want the group to be running only if the clone-fs is alive, meaning that : normal situation : clone-fs is started (do mounted) on both nodes group-res is started on node1
if clone-fs fails on node1, I want group-res to migrate on node2 same way, if res1 or res2 fails, I want group-res to migrate on node2 I've tried to play with colocation rules but it does fit my request. *What is the best way to get that behavior ?* I tried to group the res1 res2 and clone-fs together (mygroup), but it is not accepted by crm cli : group mygroup clone-fs res1 res2 meta target-role=stopped crm(live)configure# quit There are changes pending. Do you want to commit them? y element group: Relax-NG validity error : Expecting an element meta_attributes, got nothing element clone: Relax-NG validity error : Invalid sequence in interleave element clone: Relax-NG validity error : Element group failed to validate content element group: Relax-NG validity error : Element resources has extra content: group element configuration: Relax-NG validity error : Invalid sequence in interleave element cib: Relax-NG validity error : Element cib failed to validate content crm_verify[25357]: 2010/07/12_12:21:24 ERROR: main: CIB did not pass DTD/schema validation Errors found during check: config not valid Do you still want to commit? n Is it the fact that there is a clone res in the group that causes problem ? Any idea ? Thanks Alain _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
