[Pacemaker] start filesystem like this is right?

[jiaju liu]

Message: 6
Date: Sun, 14 Nov 2010 13:17:23 +0800 (CST)
From: jiaju liu <liujiaju86 at yahoo.com.cn>
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] start filesystem like this is right?
Message-ID: <476924.89659.qm at web15703.mail.cnb.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"





>>> start resource steps
>> >step(1)
>>> crm configure primitive?vol_mpath0 ocf:heartbeat:Filesystem meta target->>>role=stopped params device=/dev/mapper/mpath0 >>>directory=/mnt/mapper/mpath0 fstype='lustre' op start timeout=300s? op stop >>>timeout=120s op monitor timeout=120s interval=60s op notify timeout=60s
>>> step(2)crm resource reprobe
>
> >>step(3)
> >>crm configure location vol_mpath0_location_manage?datavol_mpath0 rule ->>inf: not_defined pingd_manage or pingd_manage lte 0
>>>
> >>crm configure location vol_mpath0_location_data?datavol_mpath0 rule -inf: >>>not_defined pingd_data or pingd_data lte 0

>>why do you have 2 location constraints? where is the definitions for
>>pingd_data and? pingd_manage?

>because we have two network. manage network is ethernet data network is ib.
?
>the definitions of pingd
>crm configure primitive pingd_data ocf:pacemaker:ping meta target-role=stopped >params name=pingd_data op start timeout=100s op stop timeout=100s op >monitor interval=90s timeout=100s";
?
>crm_resource -p host_list -r pingd_data -v IP_list
?
>crm configure clone pingd_data_net pingd_data meta globally-unique=falsetarget->role=stopped
?
>crm resource start?pingd_data
?
>crm configure primitive pingd_manage ocf:pacemaker:ping meta target->role=stopped params name=pingd_manage op start timeout=90s op stop >timeout=100s op monitor interval=90s timeout=100s
?
>crm_resource -p host_list -r pingd_manage -v IP_list
?
>crm configure clone pingd_manage_net pingd_manage meta globally->unique=false
?
>crm resource start pingd_manage

>
>>>step(4)
>> .crm resource start vol_mpath0
>
>>>delete resource steps
>
>>>.step(1)
>>>crm resource stop vol_mpath0
>>
>>>step(2)
>>>crm resource cleanup vol_mpath0
>>
>>>step(3)
>>>crm configure delete vol_mpath0
>>
>>>above?is my steps? is it right? I repeat these steps for several times. at begin >>>it works well. after 5 or 6 times the reosurce could not start .I use crm >>>resource >>start vol_mpath0 again no use.

>>Could be that your ping nodes are down?
>the node is ok. and do you know the way to check pingd? and I found the cluster >is something wrong.I check the log? I think node could not get the situation from >crm
 
 I set parameter no-quorum-policy=ignore .This is the reason?



package?are
>>> ? ? pacemaker-1.0.8-6.1.el5
>>> ? ? pacemaker-libs-devel-1.0.8-6.1.el5
>>> ? ? pacemaker-libs-1.0.8-6.1.el5
>>>
>>> ? ? openais packages?are
>>> ? ? openaislib-devel-1.1.0-1.el5
>>> ? ? openais-1.1.0-1.el5
>>> ? ? openaislib-1.1.0-1.el5
>>>
>>> ??? corosync packages are
>>> ? ? corosync-1.2.2-1.1.el5
>>> ? ? corosynclib-devel-1.2.2-1.1.el5
>>> ? ? corosynclib-1.2.2-1.1.el5
>>> ? ? who know why thanks a lot
>>>
>>>



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101115/4acdebbd/attachment-0001.html>