Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, May 11, 2015 at 10:49:45AM +0200, DRBD User wrote: > I have configured these handlers: > > fence-peer "/usr/lib/drbd/crm-fence-peer.sh"; > after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh"; > split-brain "/usr/lib/drbd/notify-split-brain.sh root"; > > pacemakers pcs poperty stonith-enabled is currently set to false It's the DLM (thus, cluster filesystem) that blocks, waiting for fencing. Which means you need pacemaker stonith-enabled=true. And you need it configured, tested, and working. You need that with any cluster file system, regardless of whether you have an actually shared or a synchronously replicated storage backend. With DRBD, you *additionally* need "fencing resource-and-stonith" on the DRBD level. -- : Lars Ellenberg : http://www.LINBIT.com | Your Way to High Availability : DRBD, Linux-HA and Pacemaker support and consulting DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed