fence-agents: master - update fence_ack_manual man page

Fabio M. Di Nitto fabbione at fedoraproject.org
Tue Apr 20 13:25:15 UTC 2010


Gitweb:        http://git.fedorahosted.org/git/fence-agents.git?p=fence-agents.git;a=commitdiff;h=cbc3aed43b6b96187c376facb24903a754249d68
Commit:        cbc3aed43b6b96187c376facb24903a754249d68
Parent:        2d7644acb8c83ee3c9ea24e0115efa49d09066ff
Author:        Fabio M. Di Nitto <fdinitto at redhat.com>
AuthorDate:    Tue Apr 20 15:21:25 2010 +0200
Committer:     Fabio M. Di Nitto <fdinitto at redhat.com>
CommitterDate: Tue Apr 20 15:21:25 2010 +0200

update fence_ack_manual man page

Signed-off-by: Fabio M. Di Nitto <fdinitto at redhat.com>
---
 fence/agents/manual/fence_ack_manual.8 |   55 +++++++++++++++++---------------
 1 files changed, 29 insertions(+), 26 deletions(-)

diff --git a/fence/agents/manual/fence_ack_manual.8 b/fence/agents/manual/fence_ack_manual.8
index e2ba505..6b4cd14 100644
--- a/fence/agents/manual/fence_ack_manual.8
+++ b/fence/agents/manual/fence_ack_manual.8
@@ -1,36 +1,39 @@
-.TH fence_ack_manual 8
+.TH FENCE_ACK_MANUAL 8 2009-12-21 cluster cluster
 
 .SH NAME
-fence_ack_manual - program run by an operator as a part of manual I/O Fencing
+fence_ack_manual \- a program to override fenced fencing operations
 
 .SH SYNOPSIS
-.B
-fence_ack_manual
-[\fIOPTION\fR]...
+.B fence_ack_manual
+[OPTIONS]
+.I nodename
 
 .SH DESCRIPTION
-fence_ack_manual is run by an operator on the same node that fence_manual(8) 
-was run after the operator has reset a node which required fencing.  A message 
-in the system log indicates to the operator that they must reset a machine and 
-then run fence_ack_manual.  Running fence_ack_manual allows the cluster to 
-continue with recovery of the fenced machine.  The victim may be disconnected 
-from storage rather than resetting it.
+When
+.BR fenced (8)
+fails to fence a node, it retries indefinately.
+.BR fence_ack_manual (8)
+tells fenced to stop retrying and consider the node fenced.
+
+.P
+It is important that this only be done after the node has been manually
+turned off or prevented from writing to shared storage.
+Without this manual action and verification, the storage that fencing
+protects may become corrupted.
+
+.P
+When fenced fences a node that has no fence devices defined in the cluster
+configuration, the fencing operation fails.  This failure will be repeated
+indefinately until fence_ack_manual is run by an operator to indicate
+the node is in a safe state to proceed.
+(Defining no fencing devices for node is the equivalent of using the
+fence_manual agent in previous versions.)
 
 .SH OPTIONS
 .TP
-\fB-h\fP
-Print out a help message describing available options, then exit.
-.TP
-\fB-O\fP
-Run without prompting for user confirmation.
-.TP
-\fB-n\fP \fInodename\fP
-Name of node that has been reset or disconnected from storage.
-.TP
-\fB-s\fP \fIIPaddress\fP
-IP address of the machine which has been reset or disconnected from storage.  (Deprecated; use -n instead.)
-.TP
-\fB-V\fP
-Print out a version message, then exit.
+.B \-h
+Print a help message describing available options, then exit.
+
 .SH SEE ALSO
-fence(8), fence_node(8)
+.BR fenced (8)
+


More information about the cluster-commits mailing list