From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 76D74FB4D for ; Mon, 24 Jul 2023 14:55:03 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4FA48ECBF for ; Mon, 24 Jul 2023 14:54:33 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Mon, 24 Jul 2023 14:54:32 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 6033B43B1D for ; Mon, 24 Jul 2023 14:54:32 +0200 (CEST) From: Aaron Lauterer To: pve-devel@lists.proxmox.com Date: Mon, 24 Jul 2023 14:54:31 +0200 Message-Id: <20230724125431.2492297-2-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20230724125431.2492297-1-a.lauterer@proxmox.com> References: <20230724125431.2492297-1-a.lauterer@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.081 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH docs 2/2] pvecm: add qdevice status flag explanation X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2023 12:55:03 -0000 They are underdocumented and finding information is not that easy. Signed-off-by: Aaron Lauterer --- Found some info in the suse documentation [0] and the sourcecode [1]. We do not ship man 3 pages, therefore I used a direct link to the github repo as that seems to be the only place that talks abit about the MW / NMW flag. [0] https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-qdevice.html [1] https://github.com/corosync/corosync/blob/v3.1.7/tools/corosync-quorumtool.c#L524-L536 pvecm.adoc | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/pvecm.adoc b/pvecm.adoc index 45271e8..e286bdd 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -1082,6 +1082,21 @@ Membership information ---- +QDevice Status Flags +^^^^^^^^^^^^^^^^^^^^ + +The status output of the QDevice, as seen above, will usually contain three +columns: + +* `A` / `NA`: Alive or Not Alive. Indicates if the communication to the external + `corosync-qndetd` daemon works. +* `V` / `NV`: If the QDevice will cast a vote for the node. In a split-brain + situation, where the corosync connection between the nodes is down, but they + both can still communicate with the external `corosync-qnetd` daemon, + only one node will get the vote. +* `MW` / `NMW`: Master wins (`MV`) or not (`NMW`). Default is `NMW`, see footnote:[`votequorum_qdevice_master_wins` manual page https://github.com/corosync/corosync/blob/main/man/votequorum_qdevice_master_wins.3.in]. +* `NR`: QDevice is not registered. + Frequently Asked Questions ~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.39.2