[16] | 1 | .TH mmdelnode 03/02/06 |
---|
| 2 | mmdelnode Command |
---|
| 3 | .SH "Name" |
---|
| 4 | .PP |
---|
| 5 | \fBmmdelnode\fR Removes one or more nodes from a GPFS cluster. |
---|
| 6 | .SH "Synopsis" |
---|
| 7 | .PP |
---|
| 8 | \fBmmdelnode\fR {\fB-a\fR | \fB-N\fR |
---|
| 9 | \fINode\fR[,\fINode\fR...] | |
---|
| 10 | \fINodeFile\fR | \fINodeClass\fR]} |
---|
| 11 | .SH "Description" |
---|
| 12 | .PP |
---|
| 13 | Use the \fBmmdelnode\fR command to delete one or more nodes from the |
---|
| 14 | GPFS cluster. You may issue the \fBmmdelnode\fR command on any GPFS |
---|
| 15 | node. |
---|
| 16 | .PP |
---|
| 17 | You must follow these rules when deleting nodes: |
---|
| 18 | .RS +3 |
---|
| 19 | .HP 3 |
---|
| 20 | 1. |
---|
| 21 | The node being deleted cannot be the primary or secondary GPFS cluster |
---|
| 22 | configuration server unless you intend to delete the entire cluster. |
---|
| 23 | Verify this by issuing the |
---|
| 24 | \fBmmlscluster\fR |
---|
| 25 | command. If a node to be deleted is one of the servers and you intend |
---|
| 26 | to keep the cluster, issue the |
---|
| 27 | \fBmmchcluster\fR |
---|
| 28 | command to assign another node as the server before deleting the node. |
---|
| 29 | .HP 3 |
---|
| 30 | 2. |
---|
| 31 | A node being deleted cannot be the primary or backup NSD server for any disk |
---|
| 32 | unless you intend to delete the entire cluster. Verify this by issuing |
---|
| 33 | the |
---|
| 34 | \fBmmlsnsd\fR command. If a node to be |
---|
| 35 | deleted is an NSD server for one or more disks, use the \fBmmchnsd\fR command to assign another node as an NSD |
---|
| 36 | server for the affected disks. |
---|
| 37 | .HP 3 |
---|
| 38 | 3. Unless all nodes in the cluster are being deleted, run the |
---|
| 39 | \fBmmdelnode\fR command from a node that will remain in the cluster. |
---|
| 40 | .HP 3 |
---|
| 41 | 4. Before you can delete a node, you must unmount all of the GPFS file |
---|
| 42 | systems and stop GPFS on the node to be deleted. |
---|
| 43 | .HP 3 |
---|
| 44 | 5. |
---|
| 45 | Exercise caution when shutting down GPFS on quorum nodes. If the number |
---|
| 46 | of remaining quorum nodes falls below the requirement for a quorum, you will |
---|
| 47 | be unable to perform file system operations. See the |
---|
| 48 | \fIGeneral Parallel File System: Concepts, |
---|
| 49 | Planning, and Installation Guide\fR and search for |
---|
| 50 | \fIquorum\fR. |
---|
| 51 | .RE |
---|
| 52 | .RS +3 |
---|
| 53 | \fBNote:\fR |
---|
| 54 | .RE |
---|
| 55 | .RS +9 |
---|
| 56 | Since each cluster is managed independently, there is no automatic |
---|
| 57 | coordination and propagation of changes between clusters like there is between |
---|
| 58 | the nodes within a cluster. This means that if you permanently delete |
---|
| 59 | nodes that are being used as contact nodes by other GPFS clusters that can |
---|
| 60 | mount your file systems, you should notify the administrators of those GPFS |
---|
| 61 | clusters so that they can update their own environments. |
---|
| 62 | .RE |
---|
| 63 | .PP |
---|
| 64 | \fBResults\fR |
---|
| 65 | .PP |
---|
| 66 | Upon successful completion of the \fBmmdelnode\fR command, the specified |
---|
| 67 | nodes are deleted from the GPFS cluster. |
---|
| 68 | .SH "Parameters" |
---|
| 69 | .PP |
---|
| 70 | .RS +3 |
---|
| 71 | \fB-a |
---|
| 72 | \fR |
---|
| 73 | .RE |
---|
| 74 | .RS +9 |
---|
| 75 | Delete all nodes in the cluster. |
---|
| 76 | .RE |
---|
| 77 | .PP |
---|
| 78 | .RS +3 |
---|
| 79 | \fB-N {\fINode\fR[,\fINode\fR...] | |
---|
| 80 | \fINodeFile\fR | \fINodeClass\fR} |
---|
| 81 | \fR |
---|
| 82 | .RE |
---|
| 83 | .RS +9 |
---|
| 84 | Specifies the set of nodes to be deleted from the cluster. For |
---|
| 85 | information on how to specify node names, see \fISpecifying nodes as input to GPFS commands\fR |
---|
| 86 | in \fIGPFS: Administration and Programming Reference\fR. |
---|
| 87 | .PP |
---|
| 88 | This command does not support a \fINodeClass\fR of |
---|
| 89 | \fBmount\fR. |
---|
| 90 | .RE |
---|
| 91 | .SH "Options" |
---|
| 92 | .PP |
---|
| 93 | None. |
---|
| 94 | .SH "Exit status" |
---|
| 95 | .PP |
---|
| 96 | .PP |
---|
| 97 | .RS +3 |
---|
| 98 | \fB0 |
---|
| 99 | \fR |
---|
| 100 | .RE |
---|
| 101 | .RS +9 |
---|
| 102 | Successful completion. |
---|
| 103 | .RE |
---|
| 104 | .PP |
---|
| 105 | .RS +3 |
---|
| 106 | \fBnonzero |
---|
| 107 | \fR |
---|
| 108 | .RE |
---|
| 109 | .RS +9 |
---|
| 110 | A failure has occurred. |
---|
| 111 | .RE |
---|
| 112 | .SH "Security" |
---|
| 113 | .PP |
---|
| 114 | You must have root authority to run the \fBmmdelnode\fR command. |
---|
| 115 | .PP |
---|
| 116 | You may issue the \fBmmdelnode\fR command from any node in the GPFS |
---|
| 117 | cluster. |
---|
| 118 | .PP |
---|
| 119 | When using the \fBrcp\fR and \fBrsh\fR commands for remote |
---|
| 120 | communication, a properly configured \fB.rhosts\fR file must exist |
---|
| 121 | in the root user's home directory on each node in the GPFS |
---|
| 122 | cluster. If you have designated the use of a different remote |
---|
| 123 | communication program on either the |
---|
| 124 | \fBmmcrcluster\fR |
---|
| 125 | or the |
---|
| 126 | \fBmmchcluster\fR command, you must |
---|
| 127 | ensure: |
---|
| 128 | .RS +3 |
---|
| 129 | .HP 3 |
---|
| 130 | 1. Proper authorization is granted to all nodes in the GPFS cluster. |
---|
| 131 | .HP 3 |
---|
| 132 | 2. The nodes in the GPFS cluster can communicate without the use of a |
---|
| 133 | password, and without any extraneous messages. |
---|
| 134 | .RE |
---|
| 135 | .SH "Examples" |
---|
| 136 | .RS +3 |
---|
| 137 | .HP 3 |
---|
| 138 | 1. To delete all of the nodes in the cluster, issue this command: |
---|
| 139 | .sp |
---|
| 140 | .nf |
---|
| 141 | mmdelnode -a |
---|
| 142 | .fi |
---|
| 143 | .sp |
---|
| 144 | The system displays information similar to: |
---|
| 145 | .sp |
---|
| 146 | .nf |
---|
| 147 | Verifying GPFS is stopped on all affected nodes ... |
---|
| 148 | mmdelnode: Command successfully completed |
---|
| 149 | mmdelnode: 6027-1371 Propagating the cluster configuration data to |
---|
| 150 | all affected nodes. This is an asynchronous process. |
---|
| 151 | .fi |
---|
| 152 | .sp |
---|
| 153 | .HP 3 |
---|
| 154 | 2. To delete nodes \fBk145n12\fR, \fBk145n13\fR, and \fBk145n14\fR, |
---|
| 155 | issue this command: |
---|
| 156 | .sp |
---|
| 157 | .nf |
---|
| 158 | mmdelnode -N k145n12,k145n13,k145n14 |
---|
| 159 | .fi |
---|
| 160 | .sp |
---|
| 161 | The system displays information similar to: |
---|
| 162 | .sp |
---|
| 163 | .nf |
---|
| 164 | Verifying GPFS is stopped on all affected nodes ... |
---|
| 165 | mmdelnode: Command successfully completed |
---|
| 166 | mmdelnode: 6027-1371 Propagating the cluster configuration data to |
---|
| 167 | all affected nodes. This is an asynchronous process. |
---|
| 168 | .fi |
---|
| 169 | .sp |
---|
| 170 | .RE |
---|
| 171 | .SH "See also" |
---|
| 172 | .PP |
---|
| 173 | mmaddnode Command |
---|
| 174 | .PP |
---|
| 175 | mmcrcluster Command |
---|
| 176 | .PP |
---|
| 177 | mmchconfig Command |
---|
| 178 | .PP |
---|
| 179 | mmlsfs Command |
---|
| 180 | .PP |
---|
| 181 | mmlscluster Command |
---|
| 182 | .SH "Location" |
---|
| 183 | .PP |
---|
| 184 | \fB/usr/lpp/mmfs/bin\fR |
---|
| 185 | .PP |
---|