URL:
Reporter RHNID:
Section: -
Language: en-US (English)
Workaround:

Description: In the creating a gfs2 practice it asks student to run

pcs property set no-quorum-policy=freeze

without explaining why

An additional description should be added to guide to explain the reasons

The following is from the gfs2 manual from the red hat documentation site

By default, the value of no-quorum-policy is set to stop, indicating that once quorum is lost, all the resources on the remaining partition will immediately be stopped. Typically this default is the safest and most optimal option, but unlike most resources, GFS2 requires quorum to function. When quorum is lost both the applications using the GFS2 mounts and the GFS2 mount itself can not be correctly stopped. Any attempts to stop these resources without quorum will fail which will ultimately result in the entire cluster being fenced every time quorum is lost.
To address this situation, you can set the no-quorum-policy=freeze when GFS2 is in use. This means that when quorum is lost, the remaining partition will do nothing until quorum is regained.