From: Aaron Lauterer Date: Tue, 25 Jul 2023 11:00:03 +0000 (+0200) Subject: pvecm: add qdevice status flag explanation X-Git-Url: https://git.proxmox.com/?a=commitdiff_plain;h=e0c0420824926034aedb6549f64d963426c9c42e;hp=50063cd726d1ba37fe303fdb82c2c9cb49d5c104;p=pve-docs.git pvecm: add qdevice status flag explanation They are underdocumented and finding information is not that easy. Signed-off-by: Aaron Lauterer [TL: break footnote with long link over multiple lines ] Signed-off-by: Thomas Lamprecht --- diff --git a/pvecm.adoc b/pvecm.adoc index 45271e8..e7759f8 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -1082,6 +1082,24 @@ Membership information ---- +[[pvecm_qdevice_status_flags]] +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://manpages.debian.org/bookworm/libvotequorum-dev/votequorum_qdevice_master_wins.3.en.html]. +* `NR`: QDevice is not registered. + Frequently Asked Questions ~~~~~~~~~~~~~~~~~~~~~~~~~~