Hi, On Mon, Mar 21, 2011 at 11:33:49PM +0100, Christoph Bartoschek wrote: > Hi, > > I am testing a NFS failover setup. During the tests I created a > split-brain situation and now node A thinks it is primary and uptodate > while node B thinks that it is Outdated. > > crm_mon however does not indicate any error to me. Why is this the case? > I expect to see anything that shows me the degraded status. How can this > be fixed?
The cluster relies on the RA (in this case drbd) to report any problems. Do you have a monitor operation defined for that resource? Thanks, Dejan > Here is the output of crm_mon: > > ============ > Last updated: Mon Mar 21 23:31:55 2011 > Stack: openais > Current DC: ries - partition with quorum > Version: 1.1.5-ecb6baaf7fc091b023d6d4ba7e0fce26d32cf5c8 > 2 Nodes configured, 2 expected votes > 4 Resources configured. > ============ > > Online: [ ries laplace ] > > Master/Slave Set: ms_drbd_nfs [p_drbd_nfs] > Masters: [ laplace ] > Slaves: [ ries ] > Clone Set: cl_lsb_nfsserver [p_lsb_nfsserver] > Started: [ laplace ries ] > Resource Group: g_nfs > p_lvm_nfs (ocf::heartbeat:LVM): Started laplace > p_fs_afs (ocf::heartbeat:Filesystem): Started laplace > p_ip_nfs (ocf::heartbeat:IPaddr2): Started laplace > Clone Set: cl_exportfs_root [p_exportfs_root] > Started: [ laplace ries ] > > > Christoph > _______________________________________________ > 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
