Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 8/29/11 4:42 PM, Digimer wrote: > On 08/29/2011 03:36 PM, William Seligman wrote: >> A general question: I have a Corosync+Pacemaker with DRBD setup on Linux; I'll >> give the details if it's relevant. Corosync+Pacemaker controls DRBD start, stop, >> and promotion. I've implemented fencing via STONITH as Corosync resources. >> >> I have not put fencing in the drbd.conf file; I was under the impression that >> Corosync+Pacemaker would take of STONITHing a node if there's a DRBD problem. Is >> this correct? Or should I have fencing/STONITH configured in both Corosync and >> drbd.conf? >> >> Does the answer change between a primary/secondary versus dual-primary setup? > > You still want to configure fencing, but you can use the > 'crm-fence-peer.sh' handler. Using this with 'resource-and-stonith' will > tell DRBD to block I/O until the fence succeeds, preventing it from > going dual-primary (even if just for the brief moment between fault and > fence). I may be dense, but I find the answer ambiguous; perhaps I didn't ask the question the right way. Let me ask in a differen way: If I have fencing set up in corosync, and corosync controls drbd, do I also need fencing in drbd.conf? -- Bill Seligman | Phone: (914) 591-2823 Nevis Labs, Columbia Univ | mailto://seligman@nevis.columbia.edu PO Box 137 | Irvington NY 10533 USA | http://www.nevis.columbia.edu/~seligman/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4497 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110830/9e690008/attachment.bin>