From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cman/man cman_tool.8
Date: 25 Sep 2007 20:10:12 -0000 [thread overview]
Message-ID: <20070925201012.14758.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: teigland at sourceware.org 2007-09-25 20:10:12
Modified files:
cman/man : cman_tool.8
Log message:
add some info about services output
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cman/man/cman_tool.8.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.4.2.4&r2=1.4.2.5
--- cluster/cman/man/cman_tool.8 2005/02/23 16:43:08 1.4.2.4
+++ cluster/cman/man/cman_tool.8 2007/09/25 20:10:12 1.4.2.5
@@ -218,3 +218,79 @@
is prepared to wait. If the operation times out then a status of 2 is returned.
Note that just because cman_tool has given up, does not mean that cman itself
has stopped trying to join a cluster.
+
+.br
+.SH "SERVICES" OUTPUT
+
+Lists the gfs, dlm, fence and rgmanager (user) groups registered locally
+with cman. Cman manages the membership of each group, and coordinates
+their recovery. The group name, global ID, local ID, State and Code are
+shown for each group. The nodeid's of the current group members are shown
+on the second line within "[ ... ]".
+
+The following details relate to the internal cman group states and can be
+useful for debugging.
+
+\fBGroup states\fP include:
+.TP 8
+.I run
+normal operation, no transition in progress
+.TP
+.I join
+local node is joining the group
+.TP
+.I update
+local node is adding/removing another node to/from the group
+.TP
+.I recover
+group is being recovered from the failure of a member
+
+
+.TP 0
+\fBRecovery codes\fP indicating the local state of recovery:
+
+.TP 2
+1
+STOP the group has been told to stop in preparation for a recovery
+.TP
+2
+START the group has been told to do recovery
+.TP
+3
+STARTDONE the group has finished recovery locally
+.TP
+4
+BARRIERWAIT the group has finished recovery locally and is waiting for
+remote nodes to finish their recovery, too
+.TP
+5
+BARRIERDONE recovery for the group has completed on all nodes, and all
+nodes have joined the completion barrier
+
+.TP 0
+\fBEvent codes\fP related to nodes joining and leaving the group. There
+are two forms these codes can take:
+
+.TP 0
+S-se_state,se_flags,se_reply_count
+.TP 4
+"S" indicates that the local node is joining or leaving the group.
+.br
+se_state is the state of the sevent, see SEST_* in sm_internal.h.
+.br
+se_flags are flags in the sevent, see SEFL_* in sm_internal.h.
+.br
+se_reply_count is the number of ack's received for the sevent.
+
+.TP 0
+U-ue_state,ue_flags,ue_nodeid
+.TP 4
+"U" indicates that the local node is processing the join or leave of
+another node.
+.br
+ue_state is the state of the uevent, see UEST_* in sm_internal.h.
+.br
+ue_flags are flags in the uevent, see UEFL_* in sm_internal.h.
+.br
+ue_nodeid is the node whose join or leave the uevent relates to.
+
next reply other threads:[~2007-09-25 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 20:10 teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-08 9:39 [Cluster-devel] cluster/cman/man cman_tool.8 pcaulfield
2007-11-08 9:36 pcaulfield
2007-10-12 18:53 rohara
2007-10-12 18:16 rohara
2007-09-17 13:59 pcaulfield
2007-08-22 13:41 teigland
2007-08-22 13:39 teigland
2007-08-22 9:34 pcaulfield
2007-08-22 9:34 pcaulfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070925201012.14758.qmail@sourceware.org \
--to=teigland@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.