Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tuesday 06 January 2009 14:18:52 GAUTIER Hervé wrote: > Peter Sabaini a écrit : > > On Tuesday 06 January 2009 10:33:33 GAUTIER Hervé wrote: > >> Unfortunately, I know well these states, but my question is in fact: > >> In case of split brain (and at any time), does DRBD know which member > >> still is or was primary ? > >> Or each peer does not keep any information concerning the other ? And it > >> will be to the clustering software to keep this information ? > > > > Hm, you probably can parse historical state data out of the kernel > > logfile; otherwise I don't know if DRBD keeps past state data. > > > > The other question is -- what are you going to do with this information? > > Have you looked at configuring the split brain recovery policy? > > Well, it is to implement a cluster manager. It will be easier if DRBD > could give me this information. Sorry, can't help you there... > > Maybe it already > > does what you want. See http://www.drbd.org/users-guide-emb/s-configure- > > split-brain-behavior.html#s-automatic-split-brain-recovery-configuration > > Not exactly. > In fact, it is to refuse to start a DRBD service in case of split brain > on a member which was not the last known (before split brain) running > the service. Isn't that what after-sb-0pri = disconnect does? peter. > Maybe dpod is the solution, but I am not sure. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090106/80c48b8a/attachment.pgp>