[Pacemaker] Pacemaker hang with hardware reset

[emmanuel segura]

I think the drbd make the fence before pacemaker and for this reason
pacemaker doesn't complete the fence request

When the problem happen give the command dlm_tool ls on the node remain up

2012/7/4 Damiano Scaramuzza <cesello at daimonlab.it>

> **
> Hi Emmanuel,
> yes I use drbd level fence as in linbit user guide
>
> disk {
>     fencing resource-only;
>     ...
>   }
>   handlers {
>     fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
>     after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
>     ...
>   }
>
> and
> the drbd driver correctly marks the peer as Outdated as soon as I reset
> the node and I suppose calls the crm-fence-peer.sh script
> to notify crm the fencing phase.
> The problem is: I see the drbd peer driver Uknown/Outdated but in crm_mon
> I still seeing both resources in Master state.
> This happens only with hard reset. If I stop and start the node I see teh
> correct phase Outdated-->UpToDate after a re-sink.
> My guess is that drbd notify, the crm try to notify but the message does
> not arrives to other components (dlm,clvm,ocfs2 )
>
>
>
>
>
> On 04/07/2012 12:22, emmanuel segura wrote:
>
> Hello Damiano
>
> Do you use drbd fence + pacemaker fence?
>
> 2012/7/4 Damiano Scaramuzza <cesello at daimonlab.it>
>
>> Hi all, my first post in this ML.
>> I've used in 2008 heartbeat for a big project and now I'm back with
>> pacemaker for a smaller one.
>> ....
>>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120704/36a54c9c/attachment.htm>