Am 31.03.2011 20:48, schrieb Dimitri Maziuk: > Christoph Bartoschek wrote: > >> ries:~ # cat /proc/drbd >> version: 8.3.9 (api:88/proto:86-95) >> srcversion: A67EB2D25C5AFBFF3D8B788 >> 0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----- >> ns:0 nr:0 dw:4 dr:1761 al:1 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:4 > >> laplace:~ # cat /proc/drbd >> version: 8.3.9 (api:88/proto:86-95) >> srcversion: A67EB2D25C5AFBFF3D8B788 >> 0: cs:StandAlone ro:Secondary/Unknown ds:Outdated/DUnknown r----- >> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:4 > > It should read "0: cs:Connected". Drbd resource should fail to start if > drbd fails to connect -- as I hinted before, the problem is more likely > in the documentation, than in pacemaker. Specifically, that it doesn't > say which of the various "wfc", "sb", "pri", "fence", and/or > "split-brain" spells to cast and what their values should be. (See > drbd.conf(5) and weep.) > > OTOH this does not seem to happen in "R1" config where drbd is started > at boot and heartbeat only handles promotion to primary and fs mount. So > this may be a genuine problem in the resource agent. > > Dima
It cannot be Connected because I did not resolve the split brain yet. The state shown is after a restart of both machines. Christoph Bartoschek _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
