[pve-devel] [PATCH v2 docs] pvecm: add qdevice status flag explanation

Aaron Lauterer a.lauterer at proxmox.com
Tue Jul 25 13:00:03 CEST 2023

They are underdocumented and finding information is not that easy.

Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
* added reference anchor for easier linking
* use link to manpages.debian.org instead of github

the corosync-doc package does ship HTML documentation, but no man pages,
    therefore only the link

 pvecm.adoc | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/pvecm.adoc b/pvecm.adoc
index 45271e8..cd8e40d 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1082,6 +1082,22 @@ Membership information
+QDevice Status Flags
+The status output of the QDevice, as seen above, will usually contain three
+* `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://manpages.debian.org/bookworm/libvotequorum-dev/votequorum_qdevice_master_wins.3.en.html].
+* `NR`: QDevice is not registered.
 Frequently Asked Questions

More information about the pve-devel mailing list