I normally just run * *
on the primary node *drbdadm primary all -d * *drbdadm connect all* *drbdadm -- --overwrite-data-of-peer primary Storage1* * * then go to the secondary and enter the following *drbdadm invalidate all* *drbdadm connect all* it forces a full sync but at least it gets it up and running Jay ** 2009/6/24 Peter Luciak <[email protected]> > Noone ever encountered a problem when starting the cluster in degraded > mode with DRBD Peer Outdater? Or I'm doing something wrong here... > > > I am facing the following problem in my v1 configuration with dopd and > STONITH: > > After consecutive shutdown of both nodes of cluster (ie. first active > node is shutdown, becomes outdated, resources are migrated to passive > node, then the passive node is shutdown as well) and starting the > outdated node _only_, the following happens: > > - node starts up with DRBD resources Secondary and Outdated (I have > wfc-timeout set) > - Heartbeat starts up, but obviously refuses to start drbd resources > thus leaving cluster nonfunctional > - during Heartbeat startup, the other node is STONITH'd which causes the > other node to boot > - after some time, both nodes are up in Secondary/Secondary > UpToDate/UpToDate > > For STONITH I'm using iLO2: > stonith_host srv1 external/riloe srv2-ilo 10.4.5.12 Administrator > password 1 2.0 off > > The whole thing seems logical, but my question is, how to avoid such > situation? :) Or, is it possible to resolve this scenario automatically, > without user intervention? > > Thanks for your time, > Peter > -- > Peter LUCIAK ([email protected]) > IBL Software Engineering, http://www.iblsoft.com/ > Mierová 103, 82105 Bratislava, Slovakia > Phone: +421-2-32662111, Fax: +421-2-32662110 > Direct: +421-2-32662175 > _______________________________________________ > 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
