The partition has been formatted and drbd works manually. Ok this is good.
But the other problem: drbd not loads the module, not mount the partition was:

<nvpair id="ma-ms-drbd0-7" name="target_role"  value="stopped"/>

I don´t remember that the resource is inittially stopped!!!



> From: [EMAIL PROTECTED]
> To: [email protected]
> Subject: Re: [Linux-HA] Hearbeat2 & DRBD8.2.
> Date: Sun, 27 Jul 2008 18:21:29 +0200
> 
> 
> On Jul 25, 2008, at 11:33 PM, ZiLioN ZilLioN wrote:
> 
> >
> >> From: [EMAIL PROTECTED]
> >> To: [email protected]
> >> Subject: Re: [Linux-HA] Hearbeat2 & DRBD8.2.
> >> Date: Fri, 25 Jul 2008 23:12:36 +0200
> >>
> >> .....
> >>>> drbd0 was Primary at this time and on this node? ... this error  
> >>>> would
> >>>> indicate that drbd0 was Secondary when Heartbeat tried to mount the
> >>>> filesystem.
> >>>
> >>> mmmm Do not heartbeat is responsible for that? Heartbear should  
> >>> set as
> >>> Primary on this node...
> >>
> >>>> You created the filesystem on /dev/drbd0 with DRBD 0.7 and now  
> >>>> upgraded
> >>>> to DRBD 8.2 ... did you also made a migration of the meta-data to  
> >>>> and
> >>>> tested DRBD without heartbeat?
> >>>
> >>> I didnŽt made a migration, I did "create-md", however the  
> >>> partition (data)
> >>
> >> .... ok, "create-md" converts the 0.7 to 8.x meta-data. so you did  
> >> upgrade
> >> (migration was the wrong term..) the meta-data ;-)
> >>
> >>> has not been formatted...
> >>>
> >>> This is section resource:
> >>>
> >>> <primitive id="drbd_mysql" class="ocf" provider="heartbeat"  
> >>> type="drbd">
> >>>      <instance_attributes>
> >>>        <attributes>
> >>>          <nvpair name="drbd_resource" value="r0"/>
> >>>        </attributes>
> >>>      </instance_attributes>
> >>>      <operations>
> >>>        <op name="monitor" interval="29s" timeout="10s"/>
> >>>      </operations>
> >>>    </primitive>
> >>>  </master_slave>
> >>>  <group id="rg_mysql">
> >>>    <primitive class="ocf" type="Filesystem"
> >>>               provider="heartbeat" id="fs_mysql">
> >>>      <instance_attributes>
> >>>        <attributes>
> >>>          <nvpair name="device" value="/dev/drbd0"/>
> >>>          <nvpair name="directory" value="/media/replica"/>
> >>>     <nvpair name="fstype" value="ext3"/> *it was fstype, it´s correct.
> >>>        </attributes>
> >>>      </instance_attributes>
> >>>    </primitive>
> >>>
> >>
> >> hmmm ... and your colocation and order constraints? drbd has to be  
> >> primary
> >> before the filesystem is mounted and the filesystem has to be  
> >> mounted on the
> >> primary node ... there is a good example ... if you really want to  
> >> go with a
> >> Master/Slave configuration:
> >
> > I have not said that the resources are members of a group. The  
> > resource drbd is the first resource, therefore the order should is  
> > correct.
> 
> i doubt this will work at all
> 
> if you're using type="drbd", then it needs to be a master/slave  
> resource.
> otherwise neither node will be allowed to mount the filesystem.
> 
> >
> >
> >>
> >> http://www.linux-ha.org/DRBD/HowTov2
> >>
> >
> > In this link has this example:
> >
> > <master_slave id="ms-drbd0">
> >         <meta_attributes id="ma-ms-drbd0">
> >           <attributes>
> >             <nvpair id="ma-ms-drbd0-1" name="clone_max" value="2"/>
> >             <nvpair id="ma-ms-drbd0-2" name="clone_node_max"  
> > value="1"/>
> >             <nvpair id="ma-ms-drbd0-3" name="master_max" value="1"/>
> >             <nvpair id="ma-ms-drbd0-4" name="master_node_max"  
> > value="1"/>
> >             <nvpair id="ma-ms-drbd0-5" name="notify" value="yes"/>
> >             <nvpair id="ma-ms-drbd0-6" name="globally_unique"  
> > value="false"/>
> >             <nvpair id="ma-ms-drbd0-7" name="target_role"  
> > value="stopped"/>
> >           </attributes>
> >         </meta_attributes>
> >         <primitive id="drbd0" class="ocf" provider="heartbeat"  
> > type="drbd">
> >           <instance_attributes id="ia-drbd0">
> >             <attributes>
> >               <nvpair id="ia-drbd0-1" name="drbd_resource"  
> > value="drbd0"/>
> >             </attributes>
> >           </instance_attributes>
> >           <operations>
> >             <op id="op-drbd0-1" name="monitor" interval="59s"  
> > timeout="10s" role="Master"/>
> >             <op id="op-drbd0-2" name="monitor" interval="60s"  
> > timeout="10s" role="Slave"/>
> >           </operations>
> >         </primitive>
> >       </master_slave>
> >
> > If I put this, The cib response is something like: This code is not  
> > a standar DTD...
> 
> it depends where you put it
> it would certainly complain it you tried to add it to a group

Yes!!! that was the reason!!!.
"ms-drbd" has been added outside the group, individually.

_________________________________________________________________
Hazte tu propia televisión a la carta. Música, noticias, estrenos, cine, humor 
y viajes en MSN Vídeo
http://video.msn.com/?mkt=es-es_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to