Bug 170926
Summary: | gfs does not respect loss of quorum (split brain?) | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Axel Thimm <axel.thimm> |
Component: | gfs | Assignee: | David Teigland <teigland> |
Status: | CLOSED DUPLICATE | QA Contact: | GFS Bugs <gfs-bugs> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-31 20:45:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Axel Thimm
2005-10-15 19:45:32 UTC
This is the correct behavior as explained in bz 162725. If a cluster loses quorum but none of the nodes mounting gfs fs "foo" have failed, then there's no need to block locking for foo (that's only needed to safely do journal recovery.) While the cluster is inquorate, no nodes are permitted to mount or unmount any gfs file systems, though. If there's a cluster partition, nodes on the inquorate side will be fenced by the quorate side before any nodes on the quorate side can mount any gfs file systems. So, if there are nodes using "foo" in an inquorate cluster, and a cluster partition gains quorum, those nodes using foo will be fenced before any nodes in the quorate cluster mount foo. *** This bug has been marked as a duplicate of 162725 *** |