[Pacemaker] Question regarding a clone resource depending on a multistate resource

Michael Schwartzkopff misch at multinet.de
Fri Jul 17 14:49:03 EDT 2009


Hi,

I configured a multistate DRBD (dual master) and OCFS2 on my cluster. I want to 
mount the filesystem where DRBD is master. The following config seems to do the 
trick:

primitive resDRBD ocf:linbit:drbd \
	operations $id="resDRBD-operations" \
	op monitor interval="20" role="Slave" timeout="20" \
	op monitor interval="10" role="Master" timeout="20" \
	params drbd_resource="r0" \
	meta $id="resDRBD-meta_attributes"
primitive resOCFS2 ocf:heartbeat:Filesystem \
	operations $id="resOCFS2-operations" \
	op monitor interval="20" timeout="40" start-delay="10" \
	params device="/dev/drbd0" directory="/mnt" fstype="ocfs2"
ms msDRBD resDRBD \
	meta clone-max="2" master-max="2" notify="true" master-node-max="1" clone-
node-max="1"
clone cloneOCFS2 resOCFS2 \
	meta interleave="true"
colocation col2OCFSDRBD inf: cloneOCFS2:Started msDRBD:Master
order ordOCFSDRBD inf: msDRBD:promote cloneOCFS2:start

when I stop one node, everything is OK. When I put that node online again I 
see the following behaviour:
1) Make the DRBD in the new-online node slave -> OK.
2) Promote the DRBD in the new-online node -> OK.
3) STOP both Filesystem resources. NOT OK!
4) Start both Filesystem resources.

Please can anybody explain, where my error is? Why do both filesystems restart 
after the promotion of the DRBD?

Here are the "LogAction" parts of the log:
Jul 17 22:30:34 debian2 pengine: [2103]: notice: LogActions: Start 
resDRBD:0#011(debian2)
Jul 17 22:30:34 debian2 pengine: [2103]: notice: LogActions: Leave resource 
resDRBD:1#011(Master debian)
Jul 17 22:30:34 debian2 pengine: [2103]: notice: LogActions: Leave resource 
resOCFS2:0#011(Stopped)
Jul 17 22:30:34 debian2 pengine: [2103]: notice: LogActions: Leave resource 
resOCFS2:1#011(Started debian)
Jul 17 22:30:38 debian2 pengine: [2103]: notice: LogActions: Promote 
resDRBD:0#011(Slave -> Master debian2)
Jul 17 22:30:38 debian2 pengine: [2103]: notice: LogActions: Leave resource 
resDRBD:1#011(Master debian)
Jul 17 22:30:38 debian2 pengine: [2103]: notice: LogActions: Start 
resOCFS2:0#011(debian)
Jul 17 22:30:38 debian2 pengine: [2103]: notice: LogActions: Move resource 
resOCFS2:1#011(Started debian -> debian2)
Jul 17 22:30:45 debian2 pengine: [2103]: notice: LogActions: Leave resource 
resDRBD:0#011(Master debian2)
Jul 17 22:30:45 debian2 pengine: [2103]: notice: LogActions: Leave resource 
resDRBD:1#011(Master debian)
Jul 17 22:30:45 debian2 pengine: [2103]: notice: LogActions: Start 
resOCFS2:0#011(debian2)
Jul 17 22:30:45 debian2 pengine: [2103]: notice: LogActions: Start 
resOCFS2:1#011(debian)


Why does the cluster migrate the resource resOCFS2:1 from node debian to 
debian2 at 22:30:38?

-- 
Dr. Michael Schwartzkopff
MultiNET Services GmbH
Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany
Tel: +49 - 89 - 45 69 11 0
Fax: +49 - 89 - 45 69 11 21
mob: +49 - 174 - 343 28 75

mail: misch at multinet.de
web: www.multinet.de

Sitz der Gesellschaft: 85630 Grasbrunn
Registergericht: Amtsgericht München HRB 114375
Geschäftsführer: Günter Jurgeneit, Hubert Martens

---

PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B
Skype: misch42




More information about the Pacemaker mailing list