<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 22, 2016 at 9:36 PM, Igor Cicimov <span dir="ltr"><<a href="mailto:icicimov@gmail.com" target="_blank">icicimov@gmail.com</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 dir="ltr">Sorry, forgot to include the list in my reply.<div><div><br><br><div><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Igor Cicimov</b> <span dir="ltr"><<a href="mailto:icicimov@gmail.com" target="_blank">icicimov@gmail.com</a>></span><br>Date: Mon, Feb 22, 2016 at 9:33 PM<br>Subject: Re: [DRBD-user] DRBD9 drbdadm complains about fencing being in wrong section<br>To: Roland Kammerer <<a href="mailto:roland.kammerer@linbit.com" target="_blank">roland.kammerer@linbit.com</a>><br><br><br><div dir="ltr">Hi Roland,<br><div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Thu, Feb 18, 2016 at 8:03 PM, Roland Kammerer <span dir="ltr"><<a href="mailto:roland.kammerer@linbit.com" target="_blank">roland.kammerer@linbit.com</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"><span>On Thu, Feb 18, 2016 at 10:37:58AM +1100, Igor Cicimov wrote:<br>
> On Wed, Feb 17, 2016 at 8:18 PM, Roland Kammerer <<a href="mailto:roland.kammerer@linbit.com" target="_blank">roland.kammerer@linbit.com</a><br>
> > wrote:<br>
><br>
> > On Wed, Feb 17, 2016 at 04:20:12PM +1100, Igor Cicimov wrote:<br>
> > > Hi,<br>
> > ><br>
> > > I'm testing 9.0.1.1 installed from git and have a resource with fencing<br>
> > in<br>
> > > the disk section:<br>
> > ><br>
> > > disk {<br>
> > > on-io-error detach;<br>
> > > fencing resource-and-stonith;<br>
> > > }<br>
> ><br>
> > It belongs to net{}, and yes, the man page is outdated, I will fix that.<br>
> ><br>
> ><br>
</span><span>> Thanks Roland that worked. By the way I'm facing another issue when<br>
> starting the service:<br>
><br>
> # service drbd start<br>
> * Starting DRBD<br>
> resources<br>
> [<br>
> create res: vg1<br>
> prepare disk: vg1<br>
> adjust disk: vg1<br>
> prepare net: vg1<br>
> adjust peer_devices: vg1<br>
> attempt to connect: vg1<br>
> ]<br>
> ...drbdadm: Unknown command 'sh-b-pri'<br>
<br>
</span>Too old version of drbd-utils (which provides the init script)?<br></blockquote><div><br></div></div></div><div>Nope, latest install from git as it can be seen in the output of the drbdadm version in my initial post.<br><br>I'm also seeing another discrepancy between the utility and what is in the docs:<br><br># drbdadm status vg1 --verbose --statistics<br>drbdadm: unrecognized option '--statistics'<br>try 'drbdadm help'<br><br></div><div>where '--statistics' is suppose to be a valid option according to the docs.<br></div><div><div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
'sh-b-pri' was dropped, see the corresponding comment in the init<br>
script:<br>
# Become primary if configured<br>
# Currently, this is necessary for drbd8<br>
# drbd9 supports automatic promote and removes the<br>
# "sh-b-pri" command.<br>
$DRBDADM sh-b-pri all || true<br>
<span><br>
><br>
> although drbdadm tells me that all is fine:<br>
><br>
> # drbdadm status<br>
> vg1 role:Primary<br>
> disk:UpToDate<br>
> drbd02 role:Primary<br>
> peer-disk:UpToDate<br>
<br>
</span>Looks good.<br>
<span><br>
><br>
> Now this is a problem since I can't set drbd under pacemaker control:<br>
><br>
> Failed actions:<br>
> p_drbd_vg1_start_0 (node=drbd01, call=9, rc=1, status=Timed Out,<br>
> last-rc-change=Thu Feb 18 10:07:43 2016<br>
> , queued=20004ms, exec=1ms<br>
> ): unknown error<br>
> p_drbd_vg1_start_0 (node=drbd02, call=9, rc=1, status=Timed Out,<br>
> last-rc-change=Thu Feb 18 10:07:43 2016<br>
> , queued=20005ms, exec=0ms<br>
> ): unknown error<br>
><br>
> I've been running this kind of setups with 8.4.4 with no issues. Has<br>
> something changed around drbd management in version 9 or is it just<br>
> something wrong with the initd script?<br>
<br>
</span>AFAIK you should not mix the drbd service with pacemaker anyways. Choose<br>
one, pacemaker. Pacemaker is really not my field of expertise, so<br>
somebody else has to jump in here.<br>
<span><br></span></blockquote><div><br></div></div></div><div>I'm not mixing them drbd is set to not autostart and should be under pacemaker control...eventually.<br> <br></div><div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>
> Finally thanks for the drbdmanage pointer I'll do some research about it (I<br>
> think I saw some presentation of yours on the web). I don't see it<br>
> installed on my system (Ubuntu 14.04.4 LTS) so guess it is not packaged<br>
> with drbd-utils but is a separate toll. I have a question though, since I<br>
> have done the config already manually, is the drbdmanage going to take over<br>
> based on already existing configuration or I will need to reconfigure<br>
> everything all over again?<br>
<br></span></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>
</span>It is a separate package and not part of drbd-utils. AFAIR downstream<br>
Debian/Ubuntu did not pick it up yet. For Ubuntu there is a PPA if you<br>
want to try it:<br>
<br>
<a href="https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack" rel="noreferrer" target="_blank">https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack</a><br>
<br>
Currently there is no importing of manually crafted res files. To me, it<br>
is actually very low on the feature list I care about. Depending on the<br>
size/time for resync/... it is probably the easiest if you start from<br>
scratch, but then it is really easy:<br>
<br>
node1-n:$ vgcreate drbdpool ...<br>
node1:$ drbdmanage init<br>
node1:$ drbdmange add-node node2 IP<br>
node1:$ drbdmange new-volume foo 10G --deploy 2<br>
<br>
<a href="http://drbd.linbit.com/users-guide-9.0/ch-admin-drbdmanage.html" rel="noreferrer" target="_blank">http://drbd.linbit.com/users-guide-9.0/ch-admin-drbdmanage.html</a><br>
<br>
And you are done, lvm configured, DRBD on top of it.<br>
<div><div><br>
Regards, rck<br>
_______________________________________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</div></div></blockquote></div></div></div><br></div></div></div>
</div><br></div></div></div></div>
</blockquote></div><br></div><div class="gmail_extra">And one more thing I find confusing. There is no drbd port listening for connections on the drbd nodes in the netstats output which I find quite strange. Maybe that is causing the pacemaker timeouts while trying to connect to drbd.<br><br>Following is the relevant part of the config:<br><br> volume 0 {<br> device /dev/drbd0;<br> disk /dev/sda;<br> meta-disk internal;<br> }<br> on drbd01 {<br> address <a href="http://10.1.1.152:7788" target="_blank">10.1.1.152:7788</a>;<br> }<br> on drbd02 {<br> address <a href="http://10.1.1.198:7788" target="_blank">10.1.1.198:7788</a>;<br> }<br> connection-mesh {<br> hosts drbd01 drbd02;<br> }<br><br></div><div class="gmail_extra">Thanks,<br></div><div class="gmail_extra">Igor<br></div></div>