source: gpfs_3.1_ker2.6.20/share/man/man8/mmadddisk.8 @ 73

Last change on this file since 73 was 16, checked in by rock, 17 years ago
File size: 9.9 KB
Line 
1.TH mmadddisk 02/16/06
2mmadddisk Command
3.SH "Name"
4.PP
5\fBmmadddisk\fR - Adds disks to a GPFS file system.
6.SH "Synopsis"
7.PP
8\fBmmadddisk\fR \fIDevice\fR
9{"\fIDiskDesc\fR[;\fIDiskDesc\fR...]"
10| \fB-F\fR \fIDescFile\fR} [\fB-a\fR]
11[\fB-r\fR] [\fB-v\fR {\fB\fIyes\fR\fR |
12\fBno\fR}] [\fB-N\fR
13{\fINode\fR[,\fINode\fR...] |
14\fINodeFile\fR | \fINodeClass\fR}]
15.SH "Description"
16.PP
17Use the \fBmmadddisk\fR command to add disks to a GPFS file
18system. This command optionally rebalances an existing file system
19after adding disks when the \fB-r\fR flag is specified. The
20\fBmmadddisk\fR command does not require the file system to be unmounted
21before issuing the command. The file system can be in use while the
22command is run.
23.PP
24\fIDevice\fR must be the first parameter.
25.PP
26The \fB-N\fR parameter can be used only in conjunction with the
27\fB-r\fR option.
28.PP
29To add disks to a GPFS file system, you first must decide if you will:
30.RS +3
31.HP 3
321. Create new disks using the
33\fBmmcrnsd\fR
34command.
35.sp
36You should also decide whether to use the rewritten disk descriptor file
37produced by the
38\fBmmcrnsd\fR command, or create a
39new list of disk descriptors. When using the rewritten file, the
40\fIDisk Usage\fR and \fIFailure Group\fR specifications will remain the
41same as specified on the
42\fBmmcrnsd\fR
43command.
44.HP 3
452. Select disks no longer in use in any file system. Issue the \fBmmlsnsd -F\fR command to display the available
46disks.
47.RE
48.SH "Parameters"
49.PP
50.RS +3
51\fB\fIDevice\fR
52\fR
53.RE
54.RS +9
55The device name of the file system to which the disks are added.
56File system names need not be fully-qualified. \fBfs0\fR is as
57acceptable as \fB/dev/fs0\fR.
58.PP
59This must be the first parameter.
60.RE
61.PP
62.RS +3
63\fB\fIDiskDesc\fR
64\fR
65.RE
66.RS +9
67A descriptor for each disk to be added. Each descriptor is
68delimited by a semicolon (;) and the entire list must be enclosed in
69quotation marks (' or ").
70.PP
71The current maximum number of disk descriptors that can be defined
72for any single file system is 268 million.
73However, to achieve this maximum limit, you must recompile GPFS.
74The actual number of disks in your file system may be
75constrained by products other than GPFS that you have
76installed. Refer to the individual product documentation.
77.PP
78A disk descriptor is defined as (second, third and sixth fields
79reserved):
80.sp
81.nf
82DiskName:::DiskUsage:FailureGroup::StoragePool:
83.fi
84.sp
85.PP
86.RS +3
87\fB\fIDiskName\fR
88\fR
89.RE
90.RS +9
91.PP
92You must specify the name of the NSD previously created by the \fBmmcrnsd\fR command. For a list of available
93disks, issue the
94\fBmmlsnsd -F\fR command.
95.RE
96.PP
97.RS +3
98\fB\fIDiskUsage\fR
99\fR
100.RE
101.RS +9
102Specify a disk usage or accept the default:
103.PP
104.RS +3
105\fBdataAndMetadata
106\fR
107.RE
108.RS +9
109Indicates that the disk contains both data and metadata. This is
110the default.
111.RE
112.PP
113.RS +3
114\fBdataOnly
115\fR
116.RE
117.RS +9
118Indicates that the disk contains data and does not contain
119metadata.
120.RE
121.PP
122.RS +3
123\fBmetadataOnly
124\fR
125.RE
126.RS +9
127Indicates that the disk contains metadata and does not contain
128data.
129.RE
130.PP
131.RS +3
132\fBdescOnly
133\fR
134.RE
135.RS +9
136Indicates that the disk contains no data and no file metadata. Such
137a disk is used solely to keep a copy of the file system descriptor, and can be
138used as a third failure group in certain disaster recovery
139configurations. For more information, see
140\fIGeneral Parallel File System: Advanced
141Administration\fR and search on \fISynchronous mirroring utilizing
142GPFS replication\fR.
143.RE
144.RE
145.PP
146.RS +3
147\fB\fIFailureGroup\fR
148\fR
149.RE
150.RS +9
151A number identifying the failure group to which this disk belongs.
152You can specify any value from -1 (where -1 indicates that the disk has no
153point of failure in common with any other disk) to 4000. If you do not
154specify a failure group, the value defaults to the NSD primary server node
155number plus 4000. If an NSD server node is not specified, the value
156defaults to -1. GPFS uses this information during data and metadata
157placement to assure that no two replicas of the same block are written in such
158a way as to become unavailable due to a single failure. All disks that
159are attached to the same NSD server or adapter should be placed in the same
160failure group.
161.PP
162If replication of \fB-m\fR or \fB-r\fR is set to
1632 for the file system, storage pools must have two failure groups for the
164commands to work properly.
165.RE
166.PP
167.RS +3
168\fB\fIStoragePool\fR
169\fR
170.RE
171.RS +9
172Specifies the storage pool to which the disk is to be assigned. If
173this name is not provided, the default is \fBsystem\fR.
174.PP
175Only the \fBsystem\fR pool may contain \fBmetadataOnly\fR,
176\fBdataAndMetadata\fR, or \fBdescOnly\fR disks.
177.RE
178.RE
179.PP
180.RS +3
181\fB-F \fIDescFile\fR
182\fR
183.RE
184.RS +9
185Specifies a file containing a list of disk descriptors, one per
186line. You may use the rewritten \fIDiskDesc\fR file created by the
187\fBmmcrnsd\fR command or create your own file.
188When using the \fIDiskDesc\fR file created by the \fBmmcrnsd\fR command, the values supplied on input to
189the command for \fIDisk Usage\fR and \fIFailureGroup \fR are
190used. When creating your own file, you must specify these values or
191accept the system defaults. A sample file can be found in
192\fB/usr/lpp/mmfs/samples/diskdesc\fR.
193.RE
194.PP
195.RS +3
196\fB-N { \fINode\fR[,\fINode\fR...]
197| \fINodeFile\fR | \fINodeClass\fR}
198\fR
199.RE
200.RS +9
201Specifies the nodes that are to participate in the restripe of the file
202system after the specified disks have been made available for use by
203GPFS. This parameter can be used only in conjunction with the \fB-r
204\fR option. This command supports all defined node classes.
205The default is \fBall\fR (all nodes in the GPFS cluster will participate in
206the restripe of the file system).
207.PP
208For information on how to specify node names, see \fISpecifying nodes as input to GPFS commands\fR
209in \fIGPFS: Administration and Programming Reference\fR.
210.RE
211.SH "Options"
212.PP
213.RS +3
214\fB-a
215\fR
216.RE
217.RS +9
218Specifies asynchronous processing. If this flag is specified, the
219\fBmmadddisk\fR command returns after the file system descriptor is updated
220and the rebalancing scan is started; it does not wait for rebalancing to
221finish. If no rebalancing is requested (the \fB-r\fR flag not
222specified), this option has no effect.
223.RE
224.PP
225.RS +3
226\fB-r
227\fR
228.RE
229.RS +9
230Rebalance all existing files in the file system to make use of new
231disks.
232.RS +3
233\fBNote:\fR
234.RE
235.RS +9
236Rebalancing of files is an I/O intensive and time consuming operation, and is
237important only for file systems with large files that are mostly
238invariant. In many cases, normal file update and creation will
239rebalance your file system over time, without the cost of the
240rebalancing.
241.RE
242.RE
243.PP
244.RS +3
245\fB-v {\fB\fIyes\fR\fR | no}
246\fR
247.RE
248.RS +9
249Verify that specified disks do not belong to an existing file
250system. The default is \fB-v yes\fR. Specify \fB-v no\fR
251only when you want to reuse disks that are no longer needed for an existing
252file system. If the command is interrupted for any reason, you must use
253the \fB-v no\fR option on the next invocation of the command.
254.RE
255.SH "Exit status"
256.PP
257.PP
258.RS +3
259\fB0
260\fR
261.RE
262.RS +9
263Successful completion.
264.RE
265.PP
266.RS +3
267\fBnonzero
268\fR
269.RE
270.RS +9
271A failure has occurred.
272.RE
273.SH "Security"
274.PP
275You must have root authority to run the \fBmmadddisk\fR command.
276.PP
277You may issue the \fBmmadddisk\fR command from any node in the GPFS
278cluster.
279.PP
280When using the \fBrcp\fR and \fBrsh\fR commands for remote
281communication, a properly configured \fB.rhosts\fR file must exist
282in the root user's home directory on each node in the GPFS
283cluster. If you have designated the use of a different remote
284communication program on the
285\fBmmcrcluster\fR or the
286\fBmmchcluster\fR command, you must ensure:
287.RS +3
288.HP 3
2891. Proper authorization is granted to all nodes in the GPFS cluster.
290.HP 3
2912. The nodes in the GPFS cluster can communicate without the use of a
292password, and without any extraneous messages.
293.RE
294.SH "Examples"
295.PP
296To add the disks whose descriptors are located in \fB./disk_pools\fR
297to the file system \fBfs1\fR, and rebalance the existing
298files after it is added, issue this command:
299.sp
300.nf
301mmadddisk fs1 -F ./disk_pools -r
302.fi
303.sp
304.PP
305The system displays information similar to:
306.sp
307.nf
308GPFS: 6027-531 The following disks of fs1 will be formatted on node
309k148n07.kgn.ibm.com:
310     gpfs10nsd: size 2202180 KB
311Extending Allocation
312Map Creating Allocation Map for storage pool 'pool2'
313   75 % complete on Thu Feb 16 13:57:52 2006 
314  100 % complete on Thu Feb 16 13:57:54 2006
315Flushing Allocation Map for storage pool 'pool2'
316GPFS: 6027-535 Disks up to size 24 GB can be added to
317storage pool pool2.
318Checking allocation map for storagepool system   
319  62 % complete on Thu Feb 16 13:58:03 2006 
320 100 % complete on Thu Feb 16 13:58:06 2006
321Checking allocation map for storage pool pool1 
322  62 % complete on Thu Feb 16 13:58:11 2006 
323 100 % complete on Thu Feb 16 13:58:14 2006
324Checking allocation map for storage pool pool2 
325  63 % complete on Thu Feb 16 13:58:19 2006 
326 100 % complete on Thu Feb 16 13:58:22 2006
327GPFS: 6027-1503 Completed adding disks to file system fs1. m
328madddisk: 6027-1371 Propagating the cluster configuration
329data to all affected nodes.  This is an asynchronous
330process.
331Restriping fs1 ...
332Thu Feb 16 13:58:48 est 2006: mmcommon pushSdr_async:
333mmsdrfs propagation started
334Thu Feb 16 13:58:52 est 2006: mmcommon pushSdr_async:
335mmsdrfs propagation completed;
336mmdsh rc = 0
337GPFS: 6027-589 Scanning file system metadata, phase 1 ... 
338GPFS: 6027-552 Scan completed successfully.
339GPFS: 6027-589 Scanning file system metadata, phase 2 ... 
340GPFS: 6027-552 Scan completed successfully.
341GPFS: 6027-589 Scanning file system metadata, phase 3 ... 
342GPFS: 6027-552 Scan completed successfully.
343GPFS: 6027-589 Scanning file system metadata, phase 4 ... 
344GPFS: 6027-552 Scan completed successfully. GPFS: 6027-565
345Scanning user file metadata ...   
346  68 %  complete on Thu Feb 16 13:59:06 2006
347 100 %  complete on Thu Feb 16 13:59:07 2006
348GPFS: 6027-552 Scan completed successfully.
349Done
350.fi
351.sp
352.SH "See also"
353.PP
354mmchdisk Command
355.PP
356mmcrnsd Command
357.PP
358mmdeldisk Command
359.PP
360mmlsdisk Command
361.PP
362mmlsnsd Command
363.SH "Location"
364.PP
365\fB/usr/lpp/mmfs/bin\fR
366.PP
Note: See TracBrowser for help on using the repository browser.