Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello,
very simple question for DRBD experts. I'm configuring Pacemaker (2 nodes Active/Standby)+DRBD shared disk with the following config:
...
disk {
fencing resource-only;
}
handlers {
fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
}...
It happen that if I poweroff the Active server (the one with DRBD Primary mounted on), the backup cannot promote and mount the DRBD anymore. This is not what I would like to happen and this problem does not occur if I remove the above fencing configuration (fencing, fence-peer and after-resync-target commands).
My only objective is to prevent promoting of a disk that is under resynch. Is there a solution? I was thinking to the following configuration:
...
disk {
fencing resource-only;
}
handlers {
before-resync-target "/usr/lib/drbd/crm-fence-peer.sh";
after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
}...
Do you think it may work, without other negative effects?
Thanks, Marco.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20170409/ddde6a1c/attachment.htm>