Mailing List Archive: Linux-HA: Pacemaker

Pacemaker will not mount ocfs2

Index | Next | Previous | View Threaded

jbergkvisth at gmail

Feb 21, 2012, 4:39 AM

Post #1 of 17 (959 views)
Permalink

Pacemaker will not mount ocfs2

I've been following this http://publications.jbfavre.org/virtualisation/cluster-
xen-corosync-pacemaker-drbd-ocfs2.en tutorial on how to setup a pacemaker xen
cluster. I'm all new to this so pls bear over with me.
The big problem is that when UI get to the pont where the filasystem should
"automagically" mount, it doesn't.

Here's my config:

node cluster01
node cluster02
primitive Cluster-FS-DLM ocf:pacemaker:controld \
op monitor interval="15" \
meta target-role="Stopped"
primitive Cluster-FS-DRBD ocf:linbit:drbd \
params drbd_resource="cluster-ocfs" \
operations $id="Cluster-FS-DRBD-ops" \
op monitor interval="20" role="Master" timeout="20" \
op monitor interval="30" role="Slave" timeout="20"
primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
params device="/dev/drbd/by-res/cluster-ocfs" directory="/cluster"
fstype="ocfs2"
ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
meta resource-stickines="100" master-max="2" notify="true"
interleave="true" target-role="Stopped"
clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
meta interleave="true" ordered="true" target-role="Stopped"
order Cluster-FS-After-DRBD inf: Cluster-FS-DRBD-Master:promote Cluster-FS-
Mount-Clone:start
order Cluster-FS-DLM-Order inf: Cluster-FS-DRBD-Master:promote Cluster-FS-Mount-
Clone:start
property $id="cib-bootstrap-options" \
dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
no-quorum-policy="ignore" \
default-resource-stickiness="1000" \
stonith-enabled="false" \
last-lrm-refresh="1329823386"

I keep getting the:
info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
scsi_hostadapter not found.
in the /var/log/syslog

I've been googling around for a solution but all of them seem to fail for me.

any help is much appreciated

Thanks Johan

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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

florian at hastexo

Feb 21, 2012, 5:26 AM

Post #2 of 17 (944 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

On 02/21/12 13:39, Johan wrote:
> I've been following this http://publications.jbfavre.org/virtualisation/cluster-
> xen-corosync-pacemaker-drbd-ocfs2.en tutorial on how to setup a pacemaker xen
> cluster. I'm all new to this so pls bear over with me.
> The big problem is that when UI get to the pont where the filasystem should
> "automagically" mount, it doesn't.
>
> Here's my config:
>
> node cluster01
> node cluster02
> primitive Cluster-FS-DLM ocf:pacemaker:controld \
> op monitor interval="15" \
> meta target-role="Stopped"
> primitive Cluster-FS-DRBD ocf:linbit:drbd \
> params drbd_resource="cluster-ocfs" \
> operations $id="Cluster-FS-DRBD-ops" \
> op monitor interval="20" role="Master" timeout="20" \
> op monitor interval="30" role="Slave" timeout="20"
> primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
> params device="/dev/drbd/by-res/cluster-ocfs" directory="/cluster"
> fstype="ocfs2"
> ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
> meta resource-stickines="100" master-max="2" notify="true"
> interleave="true" target-role="Stopped"
> clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
> meta interleave="true" ordered="true" target-role="Stopped"
> order Cluster-FS-After-DRBD inf: Cluster-FS-DRBD-Master:promote Cluster-FS-
> Mount-Clone:start
> order Cluster-FS-DLM-Order inf: Cluster-FS-DRBD-Master:promote Cluster-FS-Mount-
> Clone:start
> property $id="cib-bootstrap-options" \
> dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \
> cluster-infrastructure="openais" \
> expected-quorum-votes="2" \
> no-quorum-policy="ignore" \
> default-resource-stickiness="1000" \
> stonith-enabled="false" \
> last-lrm-refresh="1329823386"
>
> I keep getting the:
> info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
> scsi_hostadapter not found.

That's a red herring. Why the Filesystem RA is still trying to modprobe
scsi_hostadapter, and is even logging any failure to do so with a FATAL
priority, don't ask. :)

However, with all those target-role="Stopped" attributes in there
nothing of interest is really expected to start.

> in the /var/log/syslog
>
> I've been googling around for a solution but all of them seem to fail for me.
>
> any help is much appreciated

That tutorial is wrong in several places. Specifically,

"One word about OCFS2. In a perfect world, we should manage OCFS2 with
pacemaker. In this particular case, this won't be the case (I had issues
with lock managment which is mandatory for pacemaker)."

... is just nonsense. You can (and should) put the DLM and O2CB under
Pacemaker management. See the ocf:pacemaker:controld and
ocf:pacemaker:o2cb resource agents for details.

Also, you'll probably need to update your OCFS2 with "tunefs.ocfs2
--update-cluster-stack" before you can mount it.

Cheers,
Florian

--
Need help with High Availability?
http://www.hastexo.com/now

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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

florian at hastexo

Feb 21, 2012, 5:26 AM

Post #3 of 17 (944 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

jbergkvisth at gmail

Feb 21, 2012, 5:42 AM

Post #4 of 17 (952 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

Hi
Yeah I stopped them since they messed up anyway, just while looking for a
solution. I'll try the stuff you mentioned and return with a result -
thanks!
Johan

Den 21. feb. 2012 14.26 skrev Florian Haas <florian [at] hastexo>:

> On 02/21/12 13:39, Johan wrote:
> > I've been following this
> http://publications.jbfavre.org/virtualisation/cluster-
> > xen-corosync-pacemaker-drbd-ocfs2.en tutorial on how to setup a
> pacemaker xen
> > cluster. I'm all new to this so pls bear over with me.
> > The big problem is that when UI get to the pont where the filasystem
> should
> > "automagically" mount, it doesn't.
> >
> > Here's my config:
> >
> > node cluster01
> > node cluster02
> > primitive Cluster-FS-DLM ocf:pacemaker:controld \
> > op monitor interval="15" \
> > meta target-role="Stopped"
> > primitive Cluster-FS-DRBD ocf:linbit:drbd \
> > params drbd_resource="cluster-ocfs" \
> > operations $id="Cluster-FS-DRBD-ops" \
> > op monitor interval="20" role="Master" timeout="20" \
> > op monitor interval="30" role="Slave" timeout="20"
> > primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
> > params device="/dev/drbd/by-res/cluster-ocfs"
> directory="/cluster"
> > fstype="ocfs2"
> > ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
> > meta resource-stickines="100" master-max="2" notify="true"
> > interleave="true" target-role="Stopped"
> > clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
> > meta interleave="true" ordered="true" target-role="Stopped"
> > order Cluster-FS-After-DRBD inf: Cluster-FS-DRBD-Master:promote
> Cluster-FS-
> > Mount-Clone:start
> > order Cluster-FS-DLM-Order inf: Cluster-FS-DRBD-Master:promote
> Cluster-FS-Mount-
> > Clone:start
> > property $id="cib-bootstrap-options" \
> > dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \
> > cluster-infrastructure="openais" \
> > expected-quorum-votes="2" \
> > no-quorum-policy="ignore" \
> > default-resource-stickiness="1000" \
> > stonith-enabled="false" \
> > last-lrm-refresh="1329823386"
> >
> > I keep getting the:
> > info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
> > scsi_hostadapter not found.
>
> That's a red herring. Why the Filesystem RA is still trying to modprobe
> scsi_hostadapter, and is even logging any failure to do so with a FATAL
> priority, don't ask. :)
>
> However, with all those target-role="Stopped" attributes in there
> nothing of interest is really expected to start.
>
> > in the /var/log/syslog
> >
> > I've been googling around for a solution but all of them seem to fail
> for me.
> >
> > any help is much appreciated
>
> That tutorial is wrong in several places. Specifically,
>
> "One word about OCFS2. In a perfect world, we should manage OCFS2 with
> pacemaker. In this particular case, this won't be the case (I had issues
> with lock managment which is mandatory for pacemaker)."
>
> ... is just nonsense. You can (and should) put the DLM and O2CB under
> Pacemaker management. See the ocf:pacemaker:controld and
> ocf:pacemaker:o2cb resource agents for details.
>
> Also, you'll probably need to update your OCFS2 with "tunefs.ocfs2
> --update-cluster-stack" before you can mount it.
>
> Cheers,
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
>

--
MVH
Johan Bergkvist

dejanmm at fastmail

Feb 21, 2012, 7:22 AM

Post #5 of 17 (938 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

Hi,

On Tue, Feb 21, 2012 at 02:26:31PM +0100, Florian Haas wrote:
> On 02/21/12 13:39, Johan wrote:
> >
> > I keep getting the:
> > info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
> > scsi_hostadapter not found.
>
> That's a red herring. Why the Filesystem RA is still trying to modprobe
> scsi_hostadapter, and is even logging any failure to do so with a FATAL
> priority, don't ask. :)

Removed. Let's see who'll complain, then perhaps we'll know why
it was there ;-)

Dejan

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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

florian at hastexo

Feb 21, 2012, 7:31 AM

Post #6 of 17 (938 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

On Tue, Feb 21, 2012 at 4:22 PM, Dejan Muhamedagic <dejanmm [at] fastmail> wrote:
> Hi,
>
> On Tue, Feb 21, 2012 at 02:26:31PM +0100, Florian Haas wrote:
>> On 02/21/12 13:39, Johan wrote:
>> >
>> > I keep getting the:
>> > info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
>> > scsi_hostadapter not found.
>>
>> That's a red herring. Why the Filesystem RA is still trying to modprobe
>> scsi_hostadapter, and is even logging any failure to do so with a FATAL
>> priority, don't ask. :)
>
> Removed. Let's see who'll complain, then perhaps we'll know why
> it was there ;-)

Could you zap that from the Raid1 RA too, please?

Cheers,
Florian

--
Need help with High Availability?
http://www.hastexo.com/now

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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

dejanmm at fastmail

Feb 21, 2012, 10:12 PM

Post #7 of 17 (923 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

On Tue, Feb 21, 2012 at 04:31:50PM +0100, Florian Haas wrote:
> On Tue, Feb 21, 2012 at 4:22 PM, Dejan Muhamedagic <dejanmm [at] fastmail> wrote:
> > Hi,
> >
> > On Tue, Feb 21, 2012 at 02:26:31PM +0100, Florian Haas wrote:
> >> On 02/21/12 13:39, Johan wrote:
> >> >
> >> > I keep getting the:
> >> > �info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
> >> > scsi_hostadapter not found.
> >>
> >> That's a red herring. Why the Filesystem RA is still trying to modprobe
> >> scsi_hostadapter, and is even logging any failure to do so with a FATAL
> >> priority, don't ask. :)
> >
> > Removed. Let's see who'll complain, then perhaps we'll know why
> > it was there ;-)
>
> Could you zap that from the Raid1 RA too, please?

Zapped.

Cheers,

Dejan

> Cheers,
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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 [at] oss
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

jbergkvisth at gmail

Feb 22, 2012, 2:54 AM

Post #8 of 17 (926 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

Hi
So I tried to configure some dlm and o2cb resources, now I get a new error

here's the output of crm_mon

============
Last updated: Wed Feb 22 11:51:22 2012
Stack: openais
Current DC: cluster01 - partition with quorum
Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
2 Nodes configured, 2 expected votes
5 Resources configured.
============

Online: [ cluster01 cluster02 ]

ClusterIP (ocf::heartbeat:IPaddr2): Started cluster01
Master/Slave Set: Cluster-FS-DRBD-Master
Masters: [ cluster02 cluster01 ]
Clone Set: Cluster-FS-DLM-Clone
Started: [ cluster02 cluster01 ]

Failed actions:
Cluster-FS-O2CB:0_monitor_0 (node=cluster01, call=5, rc=5, status=compl
ete): not installed
Cluster-FS-O2CB:0_monitor_0 (node=cluster02, call=5, rc=5, status=compl
ete): not installed

new config looks like this:

node cluster01

node cluster02

primitive Cluster-FS-DLM ocf:pacemaker:controld \
op monitor interval="120s"

primitive Cluster-FS-DRBD ocf:linbit:drbd \
params drbd_resource="cluster-ocfs" \
operations $id="Cluster-FS-DRBD-ops" \
op monitor interval="20" role="Master" timout="20" \
op monitor interval="30" role="Slave" timeout="20"

primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
params device="/dev/drbd/by-res/cluster-ocfs"
directory="/cluster" fstype="ocfs2" \
op monitor interval="120"

primitive Cluster-FS-O2CB ocf:pacemaker:o2cb \
op monitor interval="120"

primitive ClusterIP ocf:heartbeat:IPaddr2 \
params ip="212.70.2.110" cidr_netmask="24" \
op monitor interval="30s" \
meta target-role="Started"

ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
meta resource-stickines="100" notify="true" interleave="true"
master-max="2"

clone Cluster-FS-DLM-Clone Cluster-FS-DLM \
meta globally-unique="false" interleave="true"

clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
meta interleave="true" ordered="true"

clone Cluster-FS-O2CB-Clone Cluster-FS-O2CB \
meta globally-unique="false" interleave="true"

colocation Cluster-FS-Colocation inf: Cluster-FS-DLM-Clone
Cluster-FS-DRBD-Master:Master

colocation Cluster-FS-Mount-Colocation inf: Cluster-FS-Mount-Clone
Cluster-FS-O2CB-Clone

colocation Cluster-FS-O2CB-Colocation inf: Cluster-FS-O2CB-Clone
Cluster-FS-DLM-Clone

order Cluster-FS-DLM-Order 0: Cluster-FS-DRBD-Master:promote
Cluster-FS-DLM-Clone

order Cluster-FS-Mount-Order 0: Cluster-FS-O2CB-Clone Cluster-FS-Mount-Clone

order Cluster-FS-O2CB-Order 0: Cluster-FS-DLM-Clone Cluster-FS-O2CB-Clone

I can get log output if necessary, but honestly I'm not sure what to look
for :/ I'm still new to this.

thanks

Den 22. feb. 2012 07.12 skrev Dejan Muhamedagic <dejanmm [at] fastmail>:

> On Tue, Feb 21, 2012 at 04:31:50PM +0100, Florian Haas wrote:
> > On Tue, Feb 21, 2012 at 4:22 PM, Dejan Muhamedagic <dejanmm [at] fastmail>
> wrote:
> > > Hi,
> > >
> > > On Tue, Feb 21, 2012 at 02:26:31PM +0100, Florian Haas wrote:
> > >> On 02/21/12 13:39, Johan wrote:
> > >> >
> > >> > I keep getting the:
> > >> > info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
> > >> > scsi_hostadapter not found.
> > >>
> > >> That's a red herring. Why the Filesystem RA is still trying to
> modprobe
> > >> scsi_hostadapter, and is even logging any failure to do so with a
> FATAL
> > >> priority, don't ask. :)
> > >
> > > Removed. Let's see who'll complain, then perhaps we'll know why
> > > it was there ;-)
> >
> > Could you zap that from the Raid1 RA too, please?
>
> Zapped.
>
> Cheers,
>
> Dejan
>
> > Cheers,
> > Florian
> >
> > --
> > Need help with High Availability?
> > http://www.hastexo.com/now
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker [at] oss
> > 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 [at] oss
> 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
>

--
MVH
Johan Bergkvist

emi2fast at gmail

Feb 22, 2012, 3:04 AM

Post #9 of 17 (923 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

ls -l /usr/lib/ocf/resource.d/ocfs2/o2cb
-rwxr-xr-x 1 root root 11107 2010-05-17 12:48
/usr/lib/ocf/resource.d/ocfs2/o2cb

Il giorno 22 febbraio 2012 11:54, Johan Rosing Bergkvist <
jbergkvisth [at] gmail> ha scritto:

> Hi
> So I tried to configure some dlm and o2cb resources, now I get a new error
>
> here's the output of crm_mon
>
> ============
> Last updated: Wed Feb 22 11:51:22 2012
> Stack: openais
> Current DC: cluster01 - partition with quorum
> Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
> 2 Nodes configured, 2 expected votes
> 5 Resources configured.
> ============
>
> Online: [ cluster01 cluster02 ]
>
> ClusterIP (ocf::heartbeat:IPaddr2): Started cluster01
> Master/Slave Set: Cluster-FS-DRBD-Master
> Masters: [ cluster02 cluster01 ]
> Clone Set: Cluster-FS-DLM-Clone
> Started: [ cluster02 cluster01 ]
>
> Failed actions:
> Cluster-FS-O2CB:0_monitor_0 (node=cluster01, call=5, rc=5, status=compl
> ete): not installed
> Cluster-FS-O2CB:0_monitor_0 (node=cluster02, call=5, rc=5, status=compl
> ete): not installed
>
> new config looks like this:
>
> node cluster01
>
> node cluster02
>
> primitive Cluster-FS-DLM ocf:pacemaker:controld \
> op monitor interval="120s"
>
> primitive Cluster-FS-DRBD ocf:linbit:drbd \
> params drbd_resource="cluster-ocfs" \
> operations $id="Cluster-FS-DRBD-ops" \
> op monitor interval="20" role="Master" timout="20" \
> op monitor interval="30" role="Slave" timeout="20"
>
> primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
> params device="/dev/drbd/by-res/cluster-ocfs"
> directory="/cluster" fstype="ocfs2" \
> op monitor interval="120"
>
> primitive Cluster-FS-O2CB ocf:pacemaker:o2cb \
> op monitor interval="120"
>
> primitive ClusterIP ocf:heartbeat:IPaddr2 \
> params ip="212.70.2.110" cidr_netmask="24" \
> op monitor interval="30s" \
> meta target-role="Started"
>
> ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
> meta resource-stickines="100" notify="true" interleave="true"
> master-max="2"
>
> clone Cluster-FS-DLM-Clone Cluster-FS-DLM \
> meta globally-unique="false" interleave="true"
>
> clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
> meta interleave="true" ordered="true"
>
> clone Cluster-FS-O2CB-Clone Cluster-FS-O2CB \
> meta globally-unique="false" interleave="true"
>
> colocation Cluster-FS-Colocation inf: Cluster-FS-DLM-Clone
> Cluster-FS-DRBD-Master:Master
>
> colocation Cluster-FS-Mount-Colocation inf: Cluster-FS-Mount-Clone
> Cluster-FS-O2CB-Clone
>
> colocation Cluster-FS-O2CB-Colocation inf: Cluster-FS-O2CB-Clone
> Cluster-FS-DLM-Clone
>
> order Cluster-FS-DLM-Order 0: Cluster-FS-DRBD-Master:promote
> Cluster-FS-DLM-Clone
>
> order Cluster-FS-Mount-Order 0: Cluster-FS-O2CB-Clone
> Cluster-FS-Mount-Clone
>
> order Cluster-FS-O2CB-Order 0: Cluster-FS-DLM-Clone Cluster-FS-O2CB-Clone
>
> I can get log output if necessary, but honestly I'm not sure what to look
> for :/ I'm still new to this.
>
> thanks
>
> Den 22. feb. 2012 07.12 skrev Dejan Muhamedagic <dejanmm [at] fastmail>:
>
>> On Tue, Feb 21, 2012 at 04:31:50PM +0100, Florian Haas wrote:
>> > On Tue, Feb 21, 2012 at 4:22 PM, Dejan Muhamedagic <dejanmm [at] fastmail>
>> wrote:
>> > > Hi,
>> > >
>> > > On Tue, Feb 21, 2012 at 02:26:31PM +0100, Florian Haas wrote:
>> > >> On 02/21/12 13:39, Johan wrote:
>> > >> >
>> > >> > I keep getting the:
>> > >> > info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
>> > >> > scsi_hostadapter not found.
>> > >>
>> > >> That's a red herring. Why the Filesystem RA is still trying to
>> modprobe
>> > >> scsi_hostadapter, and is even logging any failure to do so with a
>> FATAL
>> > >> priority, don't ask. :)
>> > >
>> > > Removed. Let's see who'll complain, then perhaps we'll know why
>> > > it was there ;-)
>> >
>> > Could you zap that from the Raid1 RA too, please?
>>
>> Zapped.
>>
>> Cheers,
>>
>> Dejan
>>
>> > Cheers,
>> > Florian
>> >
>> > --
>> > Need help with High Availability?
>> > http://www.hastexo.com/now
>> >
>> > _______________________________________________
>> > Pacemaker mailing list: Pacemaker [at] oss
>> > 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 [at] oss
>> 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
>>
>
>
>
> --
> MVH
> Johan Bergkvist
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
>
>

--
esta es mi vida e me la vivo hasta que dios quiera

jbergkvisth at gmail

Feb 22, 2012, 3:21 AM

Post #10 of 17 (929 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

root [at] cluster0:~# ls -l /usr/lib/ocf/resource.d/pacemaker/o2cb
-rwxr-xr-x 1 root root 10868 5 aug 2010
/usr/lib/ocf/resource.d/pacemaker/o2cb

Den 22. feb. 2012 12.04 skrev emmanuel segura <emi2fast [at] gmail>:

> ls -l /usr/lib/ocf/resource.d/ocfs2/o2cb
> -rwxr-xr-x 1 root root 11107 2010-05-17 12:48
> /usr/lib/ocf/resource.d/ocfs2/o2cb
>
>
> Il giorno 22 febbraio 2012 11:54, Johan Rosing Bergkvist <
> jbergkvisth [at] gmail> ha scritto:
>
> Hi
>> So I tried to configure some dlm and o2cb resources, now I get a new
>> error
>>
>> here's the output of crm_mon
>>
>> ============
>> Last updated: Wed Feb 22 11:51:22 2012
>> Stack: openais
>> Current DC: cluster01 - partition with quorum
>> Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
>> 2 Nodes configured, 2 expected votes
>> 5 Resources configured.
>> ============
>>
>> Online: [ cluster01 cluster02 ]
>>
>> ClusterIP (ocf::heartbeat:IPaddr2): Started cluster01
>> Master/Slave Set: Cluster-FS-DRBD-Master
>> Masters: [ cluster02 cluster01 ]
>> Clone Set: Cluster-FS-DLM-Clone
>> Started: [ cluster02 cluster01 ]
>>
>> Failed actions:
>> Cluster-FS-O2CB:0_monitor_0 (node=cluster01, call=5, rc=5,
>> status=compl
>> ete): not installed
>> Cluster-FS-O2CB:0_monitor_0 (node=cluster02, call=5, rc=5,
>> status=compl
>> ete): not installed
>>
>> new config looks like this:
>>
>> node cluster01
>>
>> node cluster02
>>
>> primitive Cluster-FS-DLM ocf:pacemaker:controld \
>> op monitor interval="120s"
>>
>> primitive Cluster-FS-DRBD ocf:linbit:drbd \
>> params drbd_resource="cluster-ocfs" \
>> operations $id="Cluster-FS-DRBD-ops" \
>> op monitor interval="20" role="Master" timout="20" \
>> op monitor interval="30" role="Slave" timeout="20"
>>
>> primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
>> params device="/dev/drbd/by-res/cluster-ocfs"
>> directory="/cluster" fstype="ocfs2" \
>> op monitor interval="120"
>>
>> primitive Cluster-FS-O2CB ocf:pacemaker:o2cb \
>> op monitor interval="120"
>>
>> primitive ClusterIP ocf:heartbeat:IPaddr2 \
>> params ip="212.70.2.110" cidr_netmask="24" \
>> op monitor interval="30s" \
>> meta target-role="Started"
>>
>> ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
>> meta resource-stickines="100" notify="true" interleave="true"
>> master-max="2"
>>
>> clone Cluster-FS-DLM-Clone Cluster-FS-DLM \
>> meta globally-unique="false" interleave="true"
>>
>> clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
>> meta interleave="true" ordered="true"
>>
>> clone Cluster-FS-O2CB-Clone Cluster-FS-O2CB \
>> meta globally-unique="false" interleave="true"
>>
>> colocation Cluster-FS-Colocation inf: Cluster-FS-DLM-Clone
>> Cluster-FS-DRBD-Master:Master
>>
>> colocation Cluster-FS-Mount-Colocation inf: Cluster-FS-Mount-Clone
>> Cluster-FS-O2CB-Clone
>>
>> colocation Cluster-FS-O2CB-Colocation inf: Cluster-FS-O2CB-Clone
>> Cluster-FS-DLM-Clone
>>
>> order Cluster-FS-DLM-Order 0: Cluster-FS-DRBD-Master:promote
>> Cluster-FS-DLM-Clone
>>
>> order Cluster-FS-Mount-Order 0: Cluster-FS-O2CB-Clone
>> Cluster-FS-Mount-Clone
>>
>> order Cluster-FS-O2CB-Order 0: Cluster-FS-DLM-Clone Cluster-FS-O2CB-Clone
>>
>> I can get log output if necessary, but honestly I'm not sure what to look
>> for :/ I'm still new to this.
>>
>> thanks
>>
>> Den 22. feb. 2012 07.12 skrev Dejan Muhamedagic <dejanmm [at] fastmail>:
>>
>>> On Tue, Feb 21, 2012 at 04:31:50PM +0100, Florian Haas wrote:
>>> > On Tue, Feb 21, 2012 at 4:22 PM, Dejan Muhamedagic <
>>> dejanmm [at] fastmail> wrote:
>>> > > Hi,
>>> > >
>>> > > On Tue, Feb 21, 2012 at 02:26:31PM +0100, Florian Haas wrote:
>>> > >> On 02/21/12 13:39, Johan wrote:
>>> > >> >
>>> > >> > I keep getting the:
>>> > >> > info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
>>> > >> > scsi_hostadapter not found.
>>> > >>
>>> > >> That's a red herring. Why the Filesystem RA is still trying to
>>> modprobe
>>> > >> scsi_hostadapter, and is even logging any failure to do so with a
>>> FATAL
>>> > >> priority, don't ask. :)
>>> > >
>>> > > Removed. Let's see who'll complain, then perhaps we'll know why
>>> > > it was there ;-)
>>> >
>>> > Could you zap that from the Raid1 RA too, please?
>>>
>>> Zapped.
>>>
>>> Cheers,
>>>
>>> Dejan
>>>
>>> > Cheers,
>>> > Florian
>>> >
>>> > --
>>> > Need help with High Availability?
>>> > http://www.hastexo.com/now
>>> >
>>> > _______________________________________________
>>> > Pacemaker mailing list: Pacemaker [at] oss
>>> > 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 [at] oss
>>> 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
>>>
>>
>>
>>
>> --
>> MVH
>> Johan Bergkvist
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker [at] oss
>> 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
>>
>>
>
>
> --
> esta es mi vida e me la vivo hasta que dios quiera
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
>
>

--
MVH
Johan Bergkvist

emi2fast at gmail

Feb 22, 2012, 3:25 AM

Post #11 of 17 (927 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

I think your order constrains are wrong

order Cluster-FS-Mount-Order 0: Cluster-FS-O2CB-Clone Cluster-FS-Mount-Clone
??????????????????????????????????
you mount the fs beafore start the dlm
??????????????????????????????????

order Cluster-FS-O2CB-Order 0: Cluster-FS-DLM-Clone Cluster-FS-O2CB-Clone

Il giorno 22 febbraio 2012 11:54, Johan Rosing Bergkvist <
jbergkvisth [at] gmail> ha scritto:

> Hi
> So I tried to configure some dlm and o2cb resources, now I get a new error
>
> here's the output of crm_mon
>
> ============
> Last updated: Wed Feb 22 11:51:22 2012
> Stack: openais
> Current DC: cluster01 - partition with quorum
> Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
> 2 Nodes configured, 2 expected votes
> 5 Resources configured.
> ============
>
> Online: [ cluster01 cluster02 ]
>
> ClusterIP (ocf::heartbeat:IPaddr2): Started cluster01
> Master/Slave Set: Cluster-FS-DRBD-Master
> Masters: [ cluster02 cluster01 ]
> Clone Set: Cluster-FS-DLM-Clone
> Started: [ cluster02 cluster01 ]
>
> Failed actions:
> Cluster-FS-O2CB:0_monitor_0 (node=cluster01, call=5, rc=5, status=compl
> ete): not installed
> Cluster-FS-O2CB:0_monitor_0 (node=cluster02, call=5, rc=5, status=compl
> ete): not installed
>
> new config looks like this:
>
> node cluster01
>
> node cluster02
>
> primitive Cluster-FS-DLM ocf:pacemaker:controld \
> op monitor interval="120s"
>
> primitive Cluster-FS-DRBD ocf:linbit:drbd \
> params drbd_resource="cluster-ocfs" \
> operations $id="Cluster-FS-DRBD-ops" \
> op monitor interval="20" role="Master" timout="20" \
> op monitor interval="30" role="Slave" timeout="20"
>
> primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
> params device="/dev/drbd/by-res/cluster-ocfs"
> directory="/cluster" fstype="ocfs2" \
> op monitor interval="120"
>
> primitive Cluster-FS-O2CB ocf:pacemaker:o2cb \
> op monitor interval="120"
>
> primitive ClusterIP ocf:heartbeat:IPaddr2 \
> params ip="212.70.2.110" cidr_netmask="24" \
> op monitor interval="30s" \
> meta target-role="Started"
>
> ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
> meta resource-stickines="100" notify="true" interleave="true"
> master-max="2"
>
> clone Cluster-FS-DLM-Clone Cluster-FS-DLM \
> meta globally-unique="false" interleave="true"
>
> clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
> meta interleave="true" ordered="true"
>
> clone Cluster-FS-O2CB-Clone Cluster-FS-O2CB \
> meta globally-unique="false" interleave="true"
>
> colocation Cluster-FS-Colocation inf: Cluster-FS-DLM-Clone
> Cluster-FS-DRBD-Master:Master
>
> colocation Cluster-FS-Mount-Colocation inf: Cluster-FS-Mount-Clone
> Cluster-FS-O2CB-Clone
>
> colocation Cluster-FS-O2CB-Colocation inf: Cluster-FS-O2CB-Clone
> Cluster-FS-DLM-Clone
>
> order Cluster-FS-DLM-Order 0: Cluster-FS-DRBD-Master:promote
> Cluster-FS-DLM-Clone
>
> order Cluster-FS-Mount-Order 0: Cluster-FS-O2CB-Clone
> Cluster-FS-Mount-Clone
>
> order Cluster-FS-O2CB-Order 0: Cluster-FS-DLM-Clone Cluster-FS-O2CB-Clone
>
> I can get log output if necessary, but honestly I'm not sure what to look
> for :/ I'm still new to this.
>
> thanks
>
> Den 22. feb. 2012 07.12 skrev Dejan Muhamedagic <dejanmm [at] fastmail>:
>
>> On Tue, Feb 21, 2012 at 04:31:50PM +0100, Florian Haas wrote:
>> > On Tue, Feb 21, 2012 at 4:22 PM, Dejan Muhamedagic <dejanmm [at] fastmail>
>> wrote:
>> > > Hi,
>> > >
>> > > On Tue, Feb 21, 2012 at 02:26:31PM +0100, Florian Haas wrote:
>> > >> On 02/21/12 13:39, Johan wrote:
>> > >> >
>> > >> > I keep getting the:
>> > >> > info: RA output: (Cluster-FS-Mount:1:start:stderr) FATAL: Module
>> > >> > scsi_hostadapter not found.
>> > >>
>> > >> That's a red herring. Why the Filesystem RA is still trying to
>> modprobe
>> > >> scsi_hostadapter, and is even logging any failure to do so with a
>> FATAL
>> > >> priority, don't ask. :)
>> > >
>> > > Removed. Let's see who'll complain, then perhaps we'll know why
>> > > it was there ;-)
>> >
>> > Could you zap that from the Raid1 RA too, please?
>>
>> Zapped.
>>
>> Cheers,
>>
>> Dejan
>>
>> > Cheers,
>> > Florian
>> >
>> > --
>> > Need help with High Availability?
>> > http://www.hastexo.com/now
>> >
>> > _______________________________________________
>> > Pacemaker mailing list: Pacemaker [at] oss
>> > 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 [at] oss
>> 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
>>
>
>
>
> --
> MVH
> Johan Bergkvist
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
>
>

--
esta es mi vida e me la vivo hasta que dios quiera

florian at hastexo

Feb 22, 2012, 3:34 AM

Post #12 of 17 (934 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

> ============
> Last updated: Wed Feb 22 11:51:22 2012
> Stack: openais
> Current DC: cluster01 - partition with quorum
> Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b

Please go to 1.1.5, at least, as soon as you can.

> primitive Cluster-FS-DLM ocf:pacemaker:controld \
> op monitor interval="120s"
>
> primitive Cluster-FS-DRBD ocf:linbit:drbd \
> params drbd_resource="cluster-ocfs" \
> operations $id="Cluster-FS-DRBD-ops" \
> op monitor interval="20" role="Master" timout="20" \
> op monitor interval="30" role="Slave" timeout="20"
>
> primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
> params device="/dev/drbd/by-res/cluster-ocfs"
> directory="/cluster" fstype="ocfs2" \
> op monitor interval="120"
>
> primitive Cluster-FS-O2CB ocf:pacemaker:o2cb \
> op monitor interval="120"
>
> primitive ClusterIP ocf:heartbeat:IPaddr2 \
> params ip="212.70.2.110" cidr_netmask="24" \
> op monitor interval="30s" \
> meta target-role="Started"
>
> ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
> meta resource-stickines="100" notify="true" interleave="true"
> master-max="2"
>
> clone Cluster-FS-DLM-Clone Cluster-FS-DLM \
> meta globally-unique="false" interleave="true"
>
> clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
> meta interleave="true" ordered="true"
>
> clone Cluster-FS-O2CB-Clone Cluster-FS-O2CB \
> meta globally-unique="false" interleave="true"
>
> colocation Cluster-FS-Colocation inf: Cluster-FS-DLM-Clone
> Cluster-FS-DRBD-Master:Master
>
> colocation Cluster-FS-Mount-Colocation inf: Cluster-FS-Mount-Clone
> Cluster-FS-O2CB-Clone
>
> colocation Cluster-FS-O2CB-Colocation inf: Cluster-FS-O2CB-Clone
> Cluster-FS-DLM-Clone
>
> order Cluster-FS-DLM-Order 0: Cluster-FS-DRBD-Master:promote
> Cluster-FS-DLM-Clone
>
> order Cluster-FS-Mount-Order 0: Cluster-FS-O2CB-Clone Cluster-FS-Mount-Clone
>
> order Cluster-FS-O2CB-Order 0: Cluster-FS-DLM-Clone Cluster-FS-O2CB-Clone

Rather than having all those individual clones and constraints between
them, you can greatly simplify your configuration with a cloned group:

primitive p_dlm_controld ocf:pacemaker:controld \
op start interval="0" timeout="90" \
op stop interval="0" timeout="100" \
op monitor interval="10"
primitive p_o2cb ocf:pacemaker:o2cb \
op start interval="0" timeout="90" \
op stop interval="0" timeout="100" \
op monitor interval="10"
primitive p_fs_ocfs2 ocf:heartbeat:Filesystem \
params device="<your drbd device>" \
directory="<your mountpoint>" \
fstype="ocfs2"
group g_ocfs2 p_dlm_controld p_o2cb p_fs_ocfs2
clone cl_ocfs2 g_ocfs2 \
meta interleave="true"

You'll still need that one order and colo constraint linking your cloned
group to the DRBD master/slave set, of course.

And if you're getting an OCF_ERR_INSTALLED error from
ocf:pacemaker:o2cb, then there definitely will be an error message in
the logs preceding that.

grep -E 'o2cb.*ERROR' /var/log/{messages,syslog}

Hope this helps.

Cheers,
Florian

--
Need help with High Availability?
http://www.hastexo.com/now

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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

jbergkvisth at gmail

Feb 23, 2012, 11:50 PM

Post #13 of 17 (915 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

Hi
Just an update.
So I upgraded to pacemaker 1.1.6 and tried to configure it all again,
without dlm.
It didn't work, I still got the " OCF_ERR_INSTALLED so I started looking
through the setup and found that I didn't specify the drbd.conf path.
When I added that meta and boom, it mounted like a dream.

Wasn't it supposed to return a OCF_ERR_CONFIGURED?

And is that meta even required?

I wonder if I messed something up(that is very likely) or maybe I missed
something.

I'll try to add the dlm today and see if it works.

Cheers.
Den 22. feb. 2012 12.34 skrev Florian Haas <florian [at] hastexo>:

> > ============
> > Last updated: Wed Feb 22 11:51:22 2012
> > Stack: openais
> > Current DC: cluster01 - partition with quorum
> > Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
>
> Please go to 1.1.5, at least, as soon as you can.
>
> > primitive Cluster-FS-DLM ocf:pacemaker:controld \
> > op monitor interval="120s"
> >
> > primitive Cluster-FS-DRBD ocf:linbit:drbd \
> > params drbd_resource="cluster-ocfs" \
> > operations $id="Cluster-FS-DRBD-ops" \
> > op monitor interval="20" role="Master" timout="20" \
> > op monitor interval="30" role="Slave" timeout="20"
> >
> > primitive Cluster-FS-Mount ocf:heartbeat:Filesystem \
> > params device="/dev/drbd/by-res/cluster-ocfs"
> > directory="/cluster" fstype="ocfs2" \
> > op monitor interval="120"
> >
> > primitive Cluster-FS-O2CB ocf:pacemaker:o2cb \
> > op monitor interval="120"
> >
> > primitive ClusterIP ocf:heartbeat:IPaddr2 \
> > params ip="212.70.2.110" cidr_netmask="24" \
> > op monitor interval="30s" \
> > meta target-role="Started"
> >
> > ms Cluster-FS-DRBD-Master Cluster-FS-DRBD \
> > meta resource-stickines="100" notify="true" interleave="true"
> > master-max="2"
> >
> > clone Cluster-FS-DLM-Clone Cluster-FS-DLM \
> > meta globally-unique="false" interleave="true"
> >
> > clone Cluster-FS-Mount-Clone Cluster-FS-Mount \
> > meta interleave="true" ordered="true"
> >
> > clone Cluster-FS-O2CB-Clone Cluster-FS-O2CB \
> > meta globally-unique="false" interleave="true"
> >
> > colocation Cluster-FS-Colocation inf: Cluster-FS-DLM-Clone
> > Cluster-FS-DRBD-Master:Master
> >
> > colocation Cluster-FS-Mount-Colocation inf: Cluster-FS-Mount-Clone
> > Cluster-FS-O2CB-Clone
> >
> > colocation Cluster-FS-O2CB-Colocation inf: Cluster-FS-O2CB-Clone
> > Cluster-FS-DLM-Clone
> >
> > order Cluster-FS-DLM-Order 0: Cluster-FS-DRBD-Master:promote
> > Cluster-FS-DLM-Clone
> >
> > order Cluster-FS-Mount-Order 0: Cluster-FS-O2CB-Clone
> Cluster-FS-Mount-Clone
> >
> > order Cluster-FS-O2CB-Order 0: Cluster-FS-DLM-Clone Cluster-FS-O2CB-Clone
>
> Rather than having all those individual clones and constraints between
> them, you can greatly simplify your configuration with a cloned group:
>
> primitive p_dlm_controld ocf:pacemaker:controld \
> op start interval="0" timeout="90" \
> op stop interval="0" timeout="100" \
> op monitor interval="10"
> primitive p_o2cb ocf:pacemaker:o2cb \
> op start interval="0" timeout="90" \
> op stop interval="0" timeout="100" \
> op monitor interval="10"
> primitive p_fs_ocfs2 ocf:heartbeat:Filesystem \
> params device="<your drbd device>" \
> directory="<your mountpoint>" \
> fstype="ocfs2"
> group g_ocfs2 p_dlm_controld p_o2cb p_fs_ocfs2
> clone cl_ocfs2 g_ocfs2 \
> meta interleave="true"
>
> You'll still need that one order and colo constraint linking your cloned
> group to the DRBD master/slave set, of course.
>
> And if you're getting an OCF_ERR_INSTALLED error from
> ocf:pacemaker:o2cb, then there definitely will be an error message in
> the logs preceding that.
>
> grep -E 'o2cb.*ERROR' /var/log/{messages,syslog}
>
> Hope this helps.
>
> Cheers,
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
>

--
MVH
Johan Bergkvist

florian at hastexo

Feb 24, 2012, 12:03 AM

Post #14 of 17 (912 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

On 02/24/12 08:50, Johan Rosing Bergkvist wrote:
> Hi
> Just an update.
> So I upgraded to pacemaker 1.1.6 and tried to configure it all again,
> without dlm.
> It didn't work, I still got the "OCF_ERR_INSTALLED so I started looking
> through the setup and found that I didn't specify the drbd.conf path.
> When I added that meta and boom, it mounted like a dream.

Huh? "drbdconf" in ocf:linbit:drbd is a regular param, not a meta
attribute. It sounds like you're mixing something up, can you clarify
please?

Cheers,
Florian

--
Need help with High Availability?
http://www.hastexo.com/now

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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

jbergkvisth at gmail

Feb 24, 2012, 12:21 AM

Post #15 of 17 (910 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

Sorry parameter, you're right.
But still It didn't mount untill I added the drbdconf parameter.

primitive clusterDRBD ocf:linbit:drbd \
params drbd_resource="cluster-ocfs" *drbdconf="/etc/drbd.conf" *#This
is what I added \
op monitor interval="20" role="Master" timeout="20" \
op monitor interval="30" role="Slave" timeout="20"

I was just wondering if this parameter was required and if so, since I used
the default path shouldn't it be preconfigured?

Second question: If it was in fact the drbdconf param that made it
"misbehave" why did it return the OCF_ERR_INSTALLED and not the
OCF_ERR_CONFIGURED (Just curious, again I might very well have missed
something.)

Sorry if I've confused you, I'm still quite green in this clustering.

Thanks for your help.

Den 24. feb. 2012 09.03 skrev Florian Haas <florian [at] hastexo>:

> On 02/24/12 08:50, Johan Rosing Bergkvist wrote:
> > Hi
> > Just an update.
> > So I upgraded to pacemaker 1.1.6 and tried to configure it all again,
> > without dlm.
> > It didn't work, I still got the "OCF_ERR_INSTALLED so I started looking
> > through the setup and found that I didn't specify the drbd.conf path.
> > When I added that meta and boom, it mounted like a dream.
>
> Huh? "drbdconf" in ocf:linbit:drbd is a regular param, not a meta
> attribute. It sounds like you're mixing something up, can you clarify
> please?
>
> Cheers,
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
>

--
MVH
Johan Bergkvist

florian at hastexo

Feb 24, 2012, 12:30 AM

Post #16 of 17 (910 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

On 02/24/12 09:21, Johan Rosing Bergkvist wrote:
> Sorry parameter, you're right.
> But still It didn't mount untill I added the drbdconf parameter.
>
> primitive clusterDRBD ocf:linbit:drbd \
> params drbd_resource="cluster-ocfs" *drbdconf="/etc/drbd.conf"
> *#This is what I added \
> op monitor interval="20" role="Master" timeout="20" \
> op monitor interval="30" role="Slave" timeout="20"
>
> I was just wondering if this parameter was required and if so, since I
> used the default path shouldn't it be preconfigured?

It is the default path, it is preconfigured, and you shouldn't need to
add this. This isn't some in-place upgrade from an age-old DRBD version
like 0.7, is it? (*shudder*)

Also, what does "ls /etc/drbd*" say?

Cheers,
Florian

--
Need help with High Availability?
http://www.hastexo.com/now

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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

jbergkvisth at gmail

Feb 24, 2012, 12:40 AM

Post #17 of 17 (922 views)
Permalink

Re: Pacemaker will not mount ocfs2 [In reply to]

Den 24. feb. 2012 09.30 skrev Florian Haas <florian [at] hastexo>:

> On 02/24/12 09:21, Johan Rosing Bergkvist wrote:
> > Sorry parameter, you're right.
> > But still It didn't mount untill I added the drbdconf parameter.
> >
> > primitive clusterDRBD ocf:linbit:drbd \
> > params drbd_resource="cluster-ocfs" *drbdconf="/etc/drbd.conf"
> > *#This is what I added \
> > op monitor interval="20" role="Master" timeout="20" \
> > op monitor interval="30" role="Slave" timeout="20"
> >
> > I was just wondering if this parameter was required and if so, since I
> > used the default path shouldn't it be preconfigured?
>
> It is the default path, it is preconfigured, and you shouldn't need to
> add this. This isn't some in-place upgrade from an age-old DRBD version
> like 0.7, is it? (*shudder*) #DRBD is a fresh install 8.3.7 from the
> Squeeze repos. Pacemaker is upgraded from 1.0.9
>
> Also, what does "ls /etc/drbd*" say?
>

> /etc/drbd.conf /etc/drbdlinks.conf
>
> /etc/drbd.d:
> global_common.conf
>
> Cheers,
> Florian
>

> THX
>
--
> Need help with High Availability?
> http://www.hastexo.com/now
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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
>

--
MVH
Johan Bergkvist

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads