File 0244-mdadm-remove-the-cluster-md-related-infos-from-doc.patch of Package mdadm.5365

From 0af023e5a4a18e7787e8811db8a588b639c33e00 Mon Sep 17 00:00:00 2001
From: Guoqing Jiang <gqjiang@suse.com>
Date: Fri, 6 Nov 2015 14:31:37 +0800
Subject: [PATCH] mdadm: remove the cluster-md related infos from doc
References: fate#316335

Since cluster-md is a EXPERIMENTAL feature for SLES-12-SP1, now we need
to delete cluster-md related infos from document and udev rule as well.

Signed-off-by: Guoqing Jiang <gqjiang@suse.com>
---
 mdadm.8.in | 42 +-----------------------------------------
 1 file changed, 1 insertion(+), 41 deletions(-)

Index: mdadm-3.3.1/mdadm.8.in
===================================================================
--- mdadm-3.3.1.orig/mdadm.8.in
+++ mdadm-3.3.1/mdadm.8.in
@@ -422,12 +422,6 @@ This functionality is currently only pro
 and
 .BR \-\-monitor .
 
-.TP
-.B \-\-home\-cluster=
-specifies the cluster name for the md device. The md device can be assembled
-only on the cluster which matches the name specified. If this option is not
-provided, mdadm tries to detect the cluster name automatically.
-
 .SH For create, build, or grow:
 
 .TP
@@ -707,12 +701,7 @@ and so is replicated on all devices.  If
 .B "none"
 is given with
 .B \-\-grow
-mode, then any bitmap that is present is removed. If the word
-.B "clustered"
-is given, the array is created for a clustered environment. One bitmap
-is created for each node as defined by the
-.B \-\-nodes
-parameter and are stored internally.
+mode, then any bitmap that is present is removed.
 
 To help catch typing errors, the filename must contain at least one
 slash ('/') if it is a real file (not 'internal' or 'none').
@@ -1005,12 +994,6 @@ the number of devices in a RAID0, it is
 number of devices, and to add the new devices, in the same command.
 
 .TP
-.BR \-\-nodes
-Only works when the array is for clustered environment. It specifies
-the maximum number of nodes in the cluster that will use this device
-simultaneously. If not specified, this defaults to 4.
-
-.TP
 .BR \-\-write-journal
 Specify journal device for the RAID-4/5/6 array. The journal device
 should be a SSD with reasonable lifetime.
@@ -1130,9 +1113,7 @@ argument given to this flag can be one o
 .BR summaries ,
 .BR uuid ,
 .BR name ,
-.BR nodes ,
 .BR homehost ,
-.BR home-cluster ,
 .BR resync ,
 .BR byteorder ,
 .BR devicesize ,
@@ -1187,13 +1168,6 @@ of the array as stored in the superblock
 version-1 superblocks.
 
 The
-.B nodes
-option will change the
-.I nodes
-of the array as stored in the bitmap superblock. This option only
-works for a clustered environment.
-
-The
 .B homehost
 option will change the
 .I homehost
@@ -1202,11 +1176,6 @@ same as updating the UUID.
 For version-1 superblocks, this involves updating the name.
 
 The
-.B home\-cluster
-option will change the cluster name as recorded in the superblock and
-bitmap. This option only works for clustered environment.
-
-The
 .B resync
 option will cause the array to be marked
 .I dirty
@@ -1453,15 +1422,6 @@ will avoid reading from these devices if
 .BR \-\-readwrite
 Subsequent devices that are added or re\-added will have the 'write-mostly'
 flag cleared.
-.TP
-.BR \-\-cluster\-confirm
-Confirm the existence of the device. This is issued in response to an \-\-add
-request by a node in a cluster. When a node adds a device it sends a message
-to all nodes in the cluster to look for a device with a UUID. This translates
-to a udev notification with the UUID of the device to be added and the slot
-number. The receiving node must acknowledge this message
-with \-\-cluster\-confirm. Valid arguments are <slot>:<devicename> in case
-the device is found or <slot>:missing in case the device is not found.
 
 .TP
 .BR \-\-failfast