Good Day,

Just trying to confirm something. Does RHEL 7 Clustering no longer accommodate for a quorum disk ?

I did a lab install and found that a disk could be used for stonith / fencing but not the traditional use for monitoring cluster status.

Very hesitant to be solely dependent on network connectivity to determine cluster status ...

Regards

Did you ever find out? Having the same very time sensitive issue for me here as well.

I even built a VM where I removed the disks (simulating fiber pull) and the cluster stayed up and running (filesystem cache?). Really would like a quorum disk. Was looking around at using sbd, however the sbd that comes in the redhat rpm comes with the "create" option disabled

Blah redhat

Any help would be appreciated. The best I could find is that redhat 7 says "you no longer need it"

ref: https://access.redhat.com/documentat...hel7-HAAR.html

Appendix A, changes from redhat 6 to redhat 7 says you no longer need quorum disk

There is no longer a quorum "disk", rather a quorum device, as in quorum service. Similar to Sun cluster's quorum service. It should be out of tech preview as of RHEL7.4

https://access.redhat.com/documentat...release_notes/
https://access.redhat.com/documentat...eference/index

SBD is not a quorum disk, it is like a message box between working nodes.
Once any node becomes defective, messages not red by this node and no fencing occur.
That is why I do not recommend to use SBD as fencing or stonith device.
You can use it do duplicate unreliable network connection to eliminate split brains.

And yes, you have a quorumd that can be configured to add vote to quorum in certain conditions, for example, ping to default gateway will add +1, scsi lock to quorum disk will add another +1, etc.