[DRBD-user] drbd handlers birng crm to unknown error!

amin dce3000 at gmail.com
Mon Jul 11 09:36:12 CEST 2011

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

hi i try to resolve drbd split brain automatically using this settings:
       handlers {

        net {
                cram-hmac-alg sha1;
                shared-secret "test";
                #after-sb-0pri discard-zero-changes;
                #after-sb-1pri discard-secondary;
                #after-sb-2pri call-pri-lost-after-sb;
                after-sb-0pri       discard-least-changes;
                after-sb-1pri       call-pri-lost-after-sb;
                after-sb-2pri       call-pri-lost-after-sb;
                rr-conflict         call-pri-lost;

while this is /usr/local/sbin/sync-unmount-reboot:

# Perform a forced reboot as safely as possible
# (contrast with reboot -f)

#mail -s drbd:forced-reboot root

    s # sync        flush any dirty buffers immediately
    u # umount      forcibly unmount fses (keeps md devs clean)
    b # reboot      initiate hardware reboot

echo 1 > /proc/sys/kernel/sysrq

for op in ${ops[@]}
do echo $op > /proc/sysrq-trigger; sleep 5

after i use any handler such what i used in this configuration pacemaker
refuse to start filesystem with unknow error! and as i clean handlers every
thing goes right.
whats wrong with using handlers aside pacemaker?
with the best regards toward you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110711/966f5e74/attachment.htm>

More information about the drbd-user mailing list