1 | .TH mmimportfs 02/16/06 |
---|
2 | mmimportfs Command |
---|
3 | .SH "Name" |
---|
4 | .PP |
---|
5 | \fBmmimportfs\fR - Imports into the cluster one or more file systems that |
---|
6 | were created in another GPFS cluster. |
---|
7 | .SH "Synopsis" |
---|
8 | .PP |
---|
9 | \fBmmimportfs\fR {\fIDevice\fR | \fBall\fR} \fB-i\fR |
---|
10 | \fIImportfsFile\fR [\fB-S\fR \fIChangeSpecFile\fR] |
---|
11 | .SH "Description" |
---|
12 | .PP |
---|
13 | The \fBmmimportfs\fR command, in conjunction with the \fBmmexportfs\fR command, can be used to move into the |
---|
14 | current GPFS cluster one or more file systems that were created in another |
---|
15 | GPFS cluster. The \fBmmimportfs\fR command extracts all relevant |
---|
16 | file system and disk information from the \fIExportFilesysData\fR file |
---|
17 | specified with the \fB-i\fR parameter. This file must have been |
---|
18 | created by the |
---|
19 | \fBmmexportfs\fR command. |
---|
20 | .PP |
---|
21 | When \fBall\fR is specified in place of a file system name, any disks |
---|
22 | that are not associated with a file system will be imported as well. |
---|
23 | .PP |
---|
24 | If the file systems being imported were created on nodes that do not |
---|
25 | belong to the current GPFS cluster, the \fBmmimportfs\fR command assumes |
---|
26 | that all disks have been properly moved, and are online and available to the |
---|
27 | appropriate nodes in the current cluster. |
---|
28 | .PP |
---|
29 | If any node in the cluster, including the node on which you are running the |
---|
30 | \fBmmimportfs\fR command, does not have access to one or more disks, use |
---|
31 | the \fB-S\fR option to assign NSD servers to those disks. |
---|
32 | .PP |
---|
33 | The \fBmmimportfs\fR command attempts to preserve any NSD server |
---|
34 | assignments that were in effect when the file system was exported. |
---|
35 | .PP |
---|
36 | If the file system was exported from a cluster created with a version of GPFS |
---|
37 | prior to 2.3, it is possible that the disks of the file system are not |
---|
38 | NSDs. Such disks will be automatically converted into NSDs by the |
---|
39 | \fBmmimportfs\fR command. |
---|
40 | .PP |
---|
41 | After the \fBmmimportfs\fR command completes, use \fBmmlsnsd\fR to display the NSD server names that are |
---|
42 | assigned to each of the disks in the imported file system. Use \fBmmchnsd\fR to change the current NSD server |
---|
43 | assignments as needed. |
---|
44 | .PP |
---|
45 | After the \fBmmimportfs\fR command completes, use \fBmmlsdisk\fR to display the failure groups to which |
---|
46 | each disk belongs. Use |
---|
47 | \fBmmchdisk\fR to make |
---|
48 | adjustments if necessary. |
---|
49 | .PP |
---|
50 | If you are importing file systems into a cluster that already contains GPFS |
---|
51 | file systems, it is possible to encounter name conflicts. You must |
---|
52 | resolve such conflicts before the \fBmmimportfs\fR command can |
---|
53 | succeed. You can use the |
---|
54 | \fBmmchfs\fR command |
---|
55 | to change the device name and mount point of an existing file system. |
---|
56 | If there are disk name conflicts, use the \fBmmcrnsd\fR command to define new disks and specify |
---|
57 | unique names (rather than let the command generate names). Then replace |
---|
58 | the conflicting disks using |
---|
59 | \fBmmrpldisk\fR and |
---|
60 | remove them from the cluster using \fBmmdelnsd\fR. |
---|
61 | .SH "Results" |
---|
62 | .PP |
---|
63 | Upon successful completion of the \fBmmimportfs\fR command, all |
---|
64 | configuration information pertaining to the file systems being imported is |
---|
65 | added to configuration data of the current GPFS cluster. |
---|
66 | .SH "Parameters" |
---|
67 | .PP |
---|
68 | .RS +3 |
---|
69 | \fB\fIDevice\fR | all |
---|
70 | \fR |
---|
71 | .RE |
---|
72 | .RS +9 |
---|
73 | The device name of the file system to be imported. File system |
---|
74 | names need not be fully-qualified. \fBfs0\fR is as acceptable as |
---|
75 | \fB/dev/fs0\fR. Specify \fBall\fR to import all GPFS file |
---|
76 | systems, as well as all disks that do not belong to a file system yet. |
---|
77 | This must be the first parameter. |
---|
78 | .RE |
---|
79 | .PP |
---|
80 | .RS +3 |
---|
81 | \fB-i \fIImportfsFile\fR |
---|
82 | \fR |
---|
83 | .RE |
---|
84 | .RS +9 |
---|
85 | The path name of the file containing the file system information. |
---|
86 | This file must have previously been created with the \fBmmexportfs\fR command. |
---|
87 | .RE |
---|
88 | .PP |
---|
89 | .RS +3 |
---|
90 | \fB-S \fIChangeSpecFile\fR |
---|
91 | \fR |
---|
92 | .RE |
---|
93 | .RS +9 |
---|
94 | The path name of an optional file containing disk descriptors, one per |
---|
95 | line, in the format: |
---|
96 | .sp |
---|
97 | .nf |
---|
98 | DiskName:PrimaryServer:BackupServer: |
---|
99 | .fi |
---|
100 | .sp |
---|
101 | .PP |
---|
102 | .RS +3 |
---|
103 | \fBDiskName |
---|
104 | \fR |
---|
105 | .RE |
---|
106 | .RS +9 |
---|
107 | The name of a disk from the file system being imported. |
---|
108 | .RE |
---|
109 | .PP |
---|
110 | .RS +3 |
---|
111 | \fBPrimaryServer |
---|
112 | \fR |
---|
113 | .RE |
---|
114 | .RS +9 |
---|
115 | The name of the primary NSD server node you want to assign to the |
---|
116 | disk. |
---|
117 | .RE |
---|
118 | .PP |
---|
119 | .RS +3 |
---|
120 | \fBBackupServer |
---|
121 | \fR |
---|
122 | .RE |
---|
123 | .RS +9 |
---|
124 | The name of the backup NSD server node you want to assign to the |
---|
125 | disk. |
---|
126 | .RE |
---|
127 | .PP |
---|
128 | \fBNotes: \fR |
---|
129 | .RS +3 |
---|
130 | .sp |
---|
131 | .HP 3 |
---|
132 | 1. You cannot change the name of a disk. You cannot change the disk |
---|
133 | usage or failure group assignment with the \fBmmimportfs\fR command. |
---|
134 | Use the |
---|
135 | \fBmmchdisk\fR command for this |
---|
136 | purpose. |
---|
137 | .sp |
---|
138 | .HP 3 |
---|
139 | 2. All disks that do not have descriptors in \fIChangeSpecFile\fR are |
---|
140 | assigned the NSD servers that they had at the time the file system was |
---|
141 | exported. All disks with NSD servers that are not valid are assumed to |
---|
142 | be SAN-attached to all nodes in the cluster. Use the \fBmmchnsd\fR command to assign new or change existing |
---|
143 | NSD server nodes. |
---|
144 | .RE |
---|
145 | .RE |
---|
146 | .SH "Exit status" |
---|
147 | .PP |
---|
148 | .PP |
---|
149 | .RS +3 |
---|
150 | \fB0 |
---|
151 | \fR |
---|
152 | .RE |
---|
153 | .RS +9 |
---|
154 | Successful completion. |
---|
155 | .RE |
---|
156 | .PP |
---|
157 | .RS +3 |
---|
158 | \fBnonzero |
---|
159 | \fR |
---|
160 | .RE |
---|
161 | .RS +9 |
---|
162 | A failure has occurred. |
---|
163 | .RE |
---|
164 | .SH "Security" |
---|
165 | .PP |
---|
166 | You must have root authority to run the \fBmmimportfs\fR command. |
---|
167 | .PP |
---|
168 | You may issue the \fBmmimportfs\fR command from any node in the GPFS |
---|
169 | cluster. |
---|
170 | .PP |
---|
171 | When using the \fBrcp\fR and \fBrsh\fR commands for remote |
---|
172 | communication, a properly configured \fB.rhosts\fR file must exist |
---|
173 | in the root user's home directory on each node in the GPFS |
---|
174 | cluster. If you have designated the use of a different remote |
---|
175 | communication program on either the |
---|
176 | \fBmmcrcluster\fR |
---|
177 | or |
---|
178 | \fBmmchcluster\fR command, you must ensure: |
---|
179 | .RS +3 |
---|
180 | .HP 3 |
---|
181 | 1. Proper authorization is granted to all nodes in the GPFS cluster. |
---|
182 | .HP 3 |
---|
183 | 2. The nodes in the GPFS cluster can communicate without the use of a |
---|
184 | password, and without any extraneous messages. |
---|
185 | .RE |
---|
186 | .SH "Examples" |
---|
187 | .PP |
---|
188 | To import all file systems in the current cluster, issue this |
---|
189 | command: |
---|
190 | .sp |
---|
191 | .nf |
---|
192 | mmimportfs all -i /u/admin/exportfile |
---|
193 | .fi |
---|
194 | .sp |
---|
195 | .PP |
---|
196 | The output is similar to this: |
---|
197 | .sp |
---|
198 | .nf |
---|
199 | mmimportfs: Processing file system fs1 ... |
---|
200 | mmimportfs: Processing disk gpfs2nsd |
---|
201 | mmimportfs: Processing disk gpfs3nsd |
---|
202 | mmimportfs: Processing disk gpfs4nsd |
---|
203 | mmimportfs: Processing file system fs2 ... |
---|
204 | mmimportfs: Processing disk gpfs1nsd1 |
---|
205 | mmimportfs: Processing disk gpfs5nsd |
---|
206 | mmimportfs: Processing disks that do not belong to any file system ... |
---|
207 | mmimportfs: Processing disk gpfs6nsd |
---|
208 | mmimportfs: Processing disk gpfs1001nsd |
---|
209 | mmimportfs: Committing the changes ... |
---|
210 | mmimportfs: The following file systems were successfully imported: |
---|
211 | fs1 |
---|
212 | fs2 |
---|
213 | mmimportfs: 6027-1371 Propagating the changes to all affected |
---|
214 | nodes. This is an asynchronous process. |
---|
215 | .fi |
---|
216 | .sp |
---|
217 | .SH "See also" |
---|
218 | .PP |
---|
219 | mmexportfs Command |
---|
220 | .SH "Location" |
---|
221 | .PP |
---|
222 | \fB/usr/lpp/mmfs/bin\fR |
---|
223 | .PP |
---|