<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi Jaco,<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 23, 2018 at 11:10 PM, Jaco van Niekerk <span dir="ltr"><<a href="mailto:jaco@desktop.co.za" target="_blank">jaco@desktop.co.za</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Hi</p>
I am using the following packages:<br>
pcs-0.9.162-5.el7.centos.1.<wbr>x86_64<br>
kmod-drbd84-8.4.11-1.el7_5.<wbr>elrepo.x86_64<br>
drbd84-utils-9.3.1-1.el7.<wbr>elrepo.x86_64<br>
pacemaker-1.1.18-11.el7_5.3.<wbr>x86_64<br>
corosync-2.4.3-2.el7_5.1.x86_<wbr>64<br>
targetcli-2.1.fb46-6.el7_5.<wbr>noarch<br>
<br>
my /etc/drbd.conf <br>
global { usage-count no; }<br>
common { protocol C; }<br>
resource imagesdata {<br>
on node1.san.localhost {<br>
device /dev/drbd0;<br>
disk /dev/vg_drbd/lv_drbd;<br>
address <a href="http://192.168.0.2:7789" target="_blank">192.168.0.2:7789</a>;<br>
meta-disk internal;<br>
}<br>
on node2.san.localhost {<br>
device /dev/drbd0;<br>
disk /dev/vg_drbd/lv_drbd;<br>
address <a href="http://192.168.0.3:7789" target="_blank">192.168.0.3:7789</a>;<br>
meta-disk internal;<br>
}<br>
}<br>
<br>
my /etc/corosync/corosync.conf:<br>
totem {<br>
version: 2<br>
secauth: off<br>
cluster_name: san_cluster<br>
transport: udpu<br>
interface {<br>
ringnumber: 0<br>
bindnetaddr: 192.168.0.0<br>
broadcast: yes<br>
mcastport: 5405<br>
}<br>
}<br>
<br>
nodelist {<br>
node {<br>
ring0_addr: node1.san.localhost<br>
name: node1<br>
nodeid: 1<br>
}<br>
<br>
node {<br>
ring0_addr: node2.san.localhost<br>
name: node2<br>
nodeid: 2<br>
}<br>
}<br>
<br>
quorum {<br>
provider: corosync_votequorum<br>
two_node: 1<br>
wait_for_all: 1<br>
last_man_standing: 1<br>
auto_tie_breaker: 0<br>
}<br>
<br>
logging {<br>
to_logfile: yes<br>
logfile: /var/log/cluster/corosync.log<br>
to_syslog: yes<br>
}<br>
<br>
Pacemaker setup:<br>
pcs cluster auth node1.san.localdomain node2.san.localdomain -u hacluster -p PASSWORD<br>
pcs cluster setup --name san_cluster node1.san.localdomain node2.san.localdomain<br>
pcs cluster start --all<br>
pcs cluster enable --all<br>
pcs property set stonith-enabled=false<br>
pcs property set no-quorum-policy=ignore<br>
<br>
The following command doesn't work:<br>
pcs resource create my_iscsidata ocf:linbit:drbd <b><div style="font-size:small;display:inline" class="gmail_default"></div><div style="font-size:small;display:inline" class="gmail_default"></div>drbd_resource=iscsidata</b> op monitor interval=10s
<br>
pcs resource master MyISCSIClone my_iscsidata master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 notify=true<br>
<br>
I receive the following on pcs status:<br>
* my_iscsidata_monitor_0 on node2.san.localhost 'not configured' (6): call=9, status=complete, exitreason='meta parameter misconfigured, expected clone-max -le 2, but found unset.',<br>
<br></div></blockquote><div> </div><div><div style="font-size:small" class="gmail_default">I guess it's a typo. See the highlighted part above, <b>drbd_resource</b> has to match your DRBD resource you created which in your case would be <b><div style="font-size:small;display:inline" class="gmail_default"><b>imagesdata</b></div></b><br></div><br></div></div></div></div>