[Linux-HA] LRM_RSC_IDLE/LRM_RSC_BUSY

Junko IKEDA ikedaj at intellilink.co.jp
Thu Oct 25 22:32:06 MDT 2007


Hi,

I tried things out about a split brain as ever,
and found the following log messages after the both nodes recovered from a
split brain.

There are two cases;

debug: do_fsa_action: actions:trace:   // A_CL_JOIN_RESULT
info: update_dc: Set DC to prec370e (2.0)
debug: do_cl_join_finalize_respond: Confirming join join-2: join_ack_nack
debug: on_msg_get_state:state of rsc prmDummy is LRM_RSC_IDLE

--- or ---

debug: do_fsa_action: actions:trace:   // A_CL_JOIN_RESULT
info: update_dc: Set DC to prec370e (2.0)
debug: do_cl_join_finalize_respond: Confirming join join-2: join_ack_nack
debug: on_msg_get_state:state of rsc prmDummy is LRM_RSC_BUSY

if the state of a resouce was LRM_RSC_IDLE,
that resource would stop nomally.

if it's LRM_RSC_BUSY,
a fail count would be increased, 
and a return code was set as 14 (EXECRA_STATUS_UNKNOWN ?).

What kind of the status of one resource in LRM_RSC_BUSY?
When would lrm regard it as LRM_RSC_BUSY?

Best Regards,
Junko Ikeda

NTT DATA INTELLILINK CORPORATION





More information about the Linux-HA mailing list