Hi again. This seems weird. I am setting a new cluster (a simpler one) and having some troubles to mount the ext3 on top of drbd partition: I get this meesages from the logs:
/var/log/messages-Jun 24 17:24:43 openvz1 Filesystem[11092]: INFO: Running start for /dev/mapper/vg0-vzpart on /mnt /var/log/messages-Jun 24 17:24:43 openvz1 lrmd: [10742]: info: RA output: (VZFS:start:stderr) mount: /dev/mapper/vg0-vzpart already mounted or /mnt busy /var/log/messages:Jun 24 17:24:43 openvz1 Filesystem[11092]: ERROR: Couldn't mount filesystem /dev/mapper/vg0-vzpart on /mnt I dont know if I missed some contrains or something like that This is the config I am testing: node $id="492edbea-b2e9-40a5-9208-bacb1bbad124" openvz1 primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="10.10.12.250" cidr_netmask="16" \ op monitor interval="30s" primitive VZData ocf:linbit:drbd \ params drbd_resource="vzpart" \ op monitor interval="60s" primitive VZFS ocf:heartbeat:Filesystem \ params device="/dev/mapper/vg0-vzpart" directory="/mnt" fstype="ext3" ms VZDataClone VZData \ meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" colocation fs_on_drbd inf: VZFS VZDataClone:Master order VZFS-after-VZData inf: VZDataClone:promote VZFS:start property $id="cib-bootstrap-options" \ dc-version="1.0.9-89bd754939df5150de7cd76835f98fe90851b677" \ cluster-infrastructure="Heartbeat" \ stonith-enabled="false" \ no-quorum-policy="ignore" \ default-action-timeout="60s" And the crm_mon for this resource Failed actions: VZFS_start_0 (node=openvz1, call=12, rc=1, status=complete): unknown error Any ideas?
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker