Ez kb. ismert viselkedése a HAST-nak, hiszen nincsen quorum funkcionalitás benne, pl. szabályos shutdown esetén (mindkét node) is a következő indításnál kézzel meg kell adni, hogy ki kicsoda. De olvasd meg a HAST man-t.
"It is possible that in the case of a connection outage between the nodes the hastd primary role for the given resource will be configured on both nodes. This in turn leads to incompatible data modifications. Such a condition is called a split-brain and cannot be automatically resolved by the hastd daemon as this will lead most likely to data corruption or loss of important changes. Even though it cannot be fixed by hastd itself, it will be detected and a further connection between independently modified nodes will not be possible. Once this situation is manually resolved by an administrator, the resource on one of the nodes can be initialized (erasing local data), which makes a connection to the remote node possi- ble again. Connection of the freshly initialized component will trigger full resource synchronization."