[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] Linux-cluster Digest, Vol 97, Issue 5


The Ip it's the last to start, as sayed before look vim /usr/share/cluster/service.sh

a have a cluster configured like that and i can tell i never found the problem

Look this, the order start of resources isn't based on the order in the xml /etc/cluster.conf, i see you work in Redhat and you don't know this Mama Mia
 <special tag="rgmanager">
        <attributes root="1" maxinstances="1"/>
        <child type="lvm" start="1" stop="9"/>
        <child type="fs" start="2" stop="8"/>
        <child type="clusterfs" start="3" stop="7"/>
        <child type="netfs" start="4" stop="6"/>
        <child type="nfsexport" start="5" stop="5"/>

        <child type="nfsclient" start="6" stop="4"/>

        <child type="ip" start="7" stop="2"/>
        <child type="smb" start="8" stop="3"/>
        <child type="script" start="9" stop="1"/>

2012/5/17 Fabio M. Di Nitto <fdinitto redhat com>
On 05/16/2012 08:20 PM, emmanuel segura wrote:

> ================================================
> it's must be
> ================================================
> <service autostart="1" domain="nfs1-domain" exclusive="0" name="nfs1"
> nfslock="1" recovery="relocate">
>                             <ip ref=""/>
>                                     <fs __independent_subtree="1"
> ref="volume01">
>                                             <nfsexport name="nfs-volume01">
>                                                     <nfsclient name=" "
> ref="local-subnet"/>
>                                             </nfsexport>
>                                     </fs>
> ================================================

That is also wrong.

<ip has to be the last one to start or you will hit race conditions at
service startup.


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

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]