I'm having some trouble on a few of my clusters in which the DRBD Slave resource does not want to come up after a reboot until I manually run resource cleanup.
Setting 'start-failure-is-fatal=false' as a global cluster property and a failure-timeout works to resolve the issue, but I don't really want the start failure set everywhere. While I work on figuring out why the slave resource isn't coming up, is it possible to set 'start-failure-is-fatal=false' only on the DRBDSlave resource, or does this need a patch? I'm running Pacemaker 1.1.12 and Corosync 1.4.8 on a RedHat 6-like system. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND ________________________________ This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
