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 {
pri-on-incon-degr
"/usr/local/sbin/sync-unmount-reboot";
pri-lost-after-sb
"/usr/local/sbin/sync-unmount-reboot";
pri-lost
"/usr/local/sbin/sync-unmount-reboot";
}
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;
allow-two-primaries;
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:
#!/bin/bash
#
# Perform a forced reboot as safely as possible
# (contrast with reboot -f)
#
#mail -s drbd:forced-reboot root
ops=(
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
done
~
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>