Hi All: Thanks for all the help (as newbies, matters a lot!). Big thanks to Jake and Andreas. We got things working.....a bit hard to tell, but we think the problem in part may have been that we set up our drbd.conf to use "dev/mapper/volumegroup-logicalvolume" for a backing device setup, and we should have been using /dev/volumegroup/logicalvolume. Does this sound right (i.e., don't use mapper)? When we used "mapper", DRBD seemed to work but not pacemaker. We think (may be wrong) that until we made this change, we couldn't get things to work. Also, we used "update-rc.d -f drbd remove" but for a backing device did not change lvm.conf (so no "filter = [ "a|drbd.*|", "r|.*|" ]").
PS: our suspicion is that that rather then DRBD as a backing device for LVM, we should probably be using DRBD as a physical volume, so may be back once we start to try that.... So as of now, our drbd.conf is: global { usage-count no; } common { syncer { rate 100M; } } #original resource r1 { protocol C; startup { wfc-timeout 15; degr-wfc-timeout 60; } device /dev/drbd1 minor 1; disk /dev/vg2/vserverLV1; meta-disk internal; # following 2 definition are equivalent on server1 { address 192.168.1.129:7801; disk /dev/vg2/vserverLV1; } on server2 { address 192.168.1.128:7801; disk /dev/vg2/vserverLV1; } # floating 192.168.5.41:7801; # floating 192.168.5.42:7801; net { cram-hmac-alg sha1; shared-secret "secret"; after-sb-0pri discard-younger-primary; #discard-zero-changes; after-sb-1pri discard-secondary; after-sb-2pri call-pri-lost-after-sb; } } And our crm configure show: node server1 node server2 primitive app_ip ocf:heartbeat:IPaddr \ params ip="192.168.1.152" \ op monitor interval="30s" primitive drbd ocf:linbit:drbd \ params drbd_resource="r1" \ op start interval="0" timeout="240" \ op stop interval="0" timeout="100" \ op monitor interval="59s" role="Master" timeout="30s" \ op monitor interval="60s" role="Slave" timeout="30s" primitive fs_vservers ocf:heartbeat:Filesystem \ params device="/dev/drbd1" directory="/vserver1" fstype="ext4" \ op start interval="0" timeout="60" \ op stop interval="0" timeout="120" ms ms_drbd drbd \ meta master-node-max="1" clone-max="2" clone-node-max="1" globally-unique="false" notify="true" target-role="Master" location drbd_on_node1 ms_drbd \ rule $id="drbd_on_node1-rule" $role="master" 100: #uname eq server1 and #uname eq server2 colocation fs_with_drbd inf: fs_vservers ms_drbd:Master order drbd_then_fs inf: ms_drbd:promote fs_vservers:start property $id="cib-bootstrap-options" \ dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" -----Original Message----- From: senrabdet <senrab...@aol.com> To: pacemaker <pacemaker@oss.clusterlabs.org> Sent: Fri, Mar 1, 2013 5:41 pm Subject: Re: [Pacemaker] Trouble with DRBD mount Thanks so much Jake (no worries-really appreciate the help) - afraid even though that statement worked, still getting same errors and drbd1 not loading at after boot...not sure what do to, maybe as said before may try rebuild....seems maybe we're doing something upstream in how we're setting up the partitions or DRBD that's causing the problems... -----Original Message----- From: Jake Smith <jsm...@argotec.com> To: The Pacemaker cluster resource manager <pacemaker@oss.clusterlabs.org> Sent: Fri, Mar 1, 2013 5:22 pm Subject: Re: [Pacemaker] Trouble with DRBD mount Sorry for the top post It should be the master slave resource in the collocation statement not the drbd primitive I.e. ms_drbd:master From: senrab...@aol.com Sent: Fri, 01/03/2013 05:12 PM To: pacemaker@oss.clusterlabs.org Subject: Re: [Pacemaker] Trouble with DRBD mount _______________________________________________ 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://bugs.clusterlabs.org _______________________________________________ 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://bugs.clusterlabs.org
_______________________________________________ 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://bugs.clusterlabs.org