I guess you did not completey do that.
[config file]
Otherwise you'd have the master colocation constraint:
<rsc_colocation id="fs0_on_drbd0" to="ms-drbd0" to_role="master"
from="fs0" score="infinity"/>
Well I did cut and paste the constraints from the website and put them
into a file but adding it with cibadmin returned me an error (as I
explained in a previous mail here in the ml); adding the two constraints
as separate files worked.
Sorry to bother again.. but there's still something wrong with my
config. If I test drbd manually I can see all the files written from
both nodes in the /dev/drbd0 block device (/dev/sda3) of the node where
it is mounted. If I use it under heartbeat every node can see only the
files it wrote.
Using it with heartbeat it reports a proc/drbd on the primary(master)
node with an unknown state for the secondary(slave)node:
version: 8.2.4 (api:88/proto:86-88)
GIT-hash: fc00c6e00a1b6039bfcebe37afa3e7e28dbd92fa build by
[EMAIL PROTECTED], 2008-02-15 13:10:55
0: cs:WFConnection st:Primary/Unknown ds:UpToDate/DUnknown C r---
ns:0 nr:0 dw:4 dr:149 al:1 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/257 hits:0 misses:1 starving:0 dirty:0 changed:1
That's not the case if I run the module/set primary/mount the directory
on my own or if I simple manage the filesystem mounting on my own and
let heartbeat run the module for me.
Can anyone help me with this?
TIA.
--
Marco.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
