You should enable this option if you are planning to use DRBD with rgmanager, the Red Hat Cluster Suite cluster resource manager. You can disable this option if you are not planning to use the Pacemaker cluster resource manager.īuild DRBD Red Hat Cluster Suite integration You can disable this option unless you are planning to use DRBD’s Heartbeat v1 resource agent or dopd. In packaging, this is typically overridden with /usr.Įven with a default prefix, most users will want to override this with /var.Įven with a default prefix, most users will want to override this with /etc.Ĭopy a rules file into your udev(7) configuration, to get symlinks named like the resources. This is the default to maintain Filesystem Hierarchy Standard compatibility for locally installed, unpackaged software. Options supported by the DRBD configure script Option Invoking the configure script with the -help option returns a full
Replay), ruling out the possibility of automatic System on the DRBD block device (even read-only), the deviceĬontents typically would be modified (for example, by file system journal Note that this is aįairly unlikely scenario. Gracefully and declare the split brain resolved. Modifications at all during split brain, DRBD will simply recover In this mode, if one of the hosts has made no Graceful recovery from split brain if one host has had no Modifications, and will then discard all modifications made on This mode, DRBD will check which of the two nodes has recorded fewer Which switched to the primary role first.ĭiscarding modifications on the primary with fewer changes. In this mode,ĭRBD will discard modifications made, in the meantime, on the node Meantime, on the node which switched to the primary role last.ĭiscarding modifications made on the older primary. Is discovered, DRBD will discard modifications made, in the Mode, when the network connection is re-established and split brain
Discarding modifications made on the younger primary.
0 kommentar(er)
