fence-agents: master - fence_scsi: Add 'unfence' to manual page

Marek GrĂ¡c marx at fedoraproject.org
Mon May 27 13:22:46 UTC 2013


Gitweb:        http://git.fedorahosted.org/git/?p=fence-agents.git;a=commitdiff;h=d6504496b019dcd6bd066dd398b898b87d4ddd49
Commit:        d6504496b019dcd6bd066dd398b898b87d4ddd49
Parent:        cda15e4940779111aa69aa29da705ae91b789a83
Author:        Marek 'marx' Grac <mgrac at redhat.com>
AuthorDate:    Mon May 27 15:19:59 2013 +0200
Committer:     Marek 'marx' Grac <mgrac at redhat.com>
CommitterDate: Mon May 27 15:19:59 2013 +0200

fence_scsi: Add 'unfence' to manual page

Resolves: rhbz#887349
---
 fence/agents/scsi/fence_scsi.8 |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/fence/agents/scsi/fence_scsi.8 b/fence/agents/scsi/fence_scsi.8
index 0d70930..da2e451 100644
--- a/fence/agents/scsi/fence_scsi.8
+++ b/fence/agents/scsi/fence_scsi.8
@@ -21,7 +21,8 @@ registrants only" reservation on the device(s). The result is that
 only registered nodes may write to the device(s). When a node failure
 occurs, the fence_scsi agent will remove the key belonging to the
 failed node from the device(s). The failed node will no longer be able
-to write to the device(s). A manual reboot is required.
+to write to the device(s). A manual reboot is required. In the cluster
+environment unfence action should be configured also.
 
 Keys are either be specified manually (see -k option) or generated
 automatically (see -n option). Automatic key generation requires that


More information about the cluster-commits mailing list