Hi, On Fri, Oct 26, 2007 at 01:32:06PM +0900, Junko IKEDA wrote: > 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 ?).
That should not have anything to do with it. If the resource is busy, the requested operation will be postponed until it becomes idle. The CRM handles such a situation. > What kind of the status of one resource in LRM_RSC_BUSY? > When would lrm regard it as LRM_RSC_BUSY? A resource is busy whenever there's an operation running, i.e. such as monitor. Idle is the opposite. Thanks, Dejan > Best Regards, > Junko Ikeda > > NTT DATA INTELLILINK CORPORATION > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
