1 | .TH mmumount 12/04/06 |
---|
2 | mmumount Command |
---|
3 | .SH "Name" |
---|
4 | .PP |
---|
5 | \fBmmumount\fR - Unmounts GPFS file systems on one or more nodes in |
---|
6 | the cluster. |
---|
7 | .SH "Synopsis" |
---|
8 | .PP |
---|
9 | \fBmmumount\fR \fB{\fR\fIDevice\fR\fB | |
---|
10 | \fR\fIMountPoint\fR\fB | all | all_local | all_remote}\fR \fB[-f |
---|
11 | ]\fR \fB[-a | -N |
---|
12 | \fR\fB{\fR\fINode\fR\fB[,\fR\fINode\fR\fB...] |
---|
13 | | \fR\fINodeFile\fR\fB | \fR\fINodeClass\fR\fB}]\fR |
---|
14 | .PP |
---|
15 | Or, |
---|
16 | .PP |
---|
17 | \fBmmumount \fR\fIDevice\fR\fB -f -C {all_remote | |
---|
18 | \fR\fIClusterName\fR\fB} [-N |
---|
19 | \fR\fINode\fR\fB[,\fR\fINode\fR\fB...]]\fR |
---|
20 | .SH "Description" |
---|
21 | .PP |
---|
22 | Another name for the \fBmmumount\fR command is the \fBmmunmount\fR |
---|
23 | command. Either name can be used. |
---|
24 | .PP |
---|
25 | The \fBmmumount\fR command unmounts a previously mounted GPFS file |
---|
26 | system on one or more nodes in the cluster. If no nodes are specified, |
---|
27 | the file systems are unmounted only on the node from which the command was |
---|
28 | issued. The file system can be specified using its device name or the |
---|
29 | mount point where it is currently mounted. |
---|
30 | .PP |
---|
31 | The first form of the command should be used to unmount file systems on |
---|
32 | nodes that belong to the local cluster. |
---|
33 | .PP |
---|
34 | The second form of the command (-C option) should be used when it is |
---|
35 | necessary to internally force unmount file systems that are owned by this |
---|
36 | cluster but are mounted on nodes that belong to another cluster. |
---|
37 | .PP |
---|
38 | When a file system is internally force unmounted with the second form of |
---|
39 | the \fBmmumount\fR command, the affected nodes may still show the file |
---|
40 | system as mounted but the data will not be accessible. It is the |
---|
41 | responsibility of the system administrator to clear the mount state by issuing |
---|
42 | the \fBumount\fR command. |
---|
43 | .SH "Parameters" |
---|
44 | .PP |
---|
45 | .RS +3 |
---|
46 | \fB\fIDevice\fR | all | all_local | all_remote |
---|
47 | \fR |
---|
48 | .RE |
---|
49 | .RS +9 |
---|
50 | .PP |
---|
51 | .RS +3 |
---|
52 | \fB\fIDevice\fR |
---|
53 | \fR |
---|
54 | .RE |
---|
55 | .RS +9 |
---|
56 | The device name of the file system to be unmounted. File system |
---|
57 | names do not need to be fully-qualified. \fBfs0\fR is just as |
---|
58 | acceptable as \fB/dev/fs0\fR. |
---|
59 | .RE |
---|
60 | .PP |
---|
61 | .RS +3 |
---|
62 | \fBall |
---|
63 | \fR |
---|
64 | .RE |
---|
65 | .RS +9 |
---|
66 | Indicates all file systems known to this cluster |
---|
67 | .RE |
---|
68 | .PP |
---|
69 | .RS +3 |
---|
70 | \fBall_local |
---|
71 | \fR |
---|
72 | .RE |
---|
73 | .RS +9 |
---|
74 | Indicates all file systems owned by this cluster |
---|
75 | .RE |
---|
76 | .PP |
---|
77 | .RS +3 |
---|
78 | \fBall_remote |
---|
79 | \fR |
---|
80 | .RE |
---|
81 | .RS +9 |
---|
82 | Indicates all files systems owned by another cluster to which this cluster |
---|
83 | has access |
---|
84 | .RE |
---|
85 | .PP |
---|
86 | This must be the first parameter. |
---|
87 | .RE |
---|
88 | .PP |
---|
89 | .RS +3 |
---|
90 | \fB\fIMountPoint\fR |
---|
91 | \fR |
---|
92 | .RE |
---|
93 | .RS +9 |
---|
94 | The location where the GPFS file system to be unmounted is currently |
---|
95 | mounted. |
---|
96 | .RE |
---|
97 | .SH "Options" |
---|
98 | .PP |
---|
99 | .RS +3 |
---|
100 | \fB-a |
---|
101 | \fR |
---|
102 | .RE |
---|
103 | .RS +9 |
---|
104 | Unmount the file system on all nodes in the GPFS cluster. |
---|
105 | .RE |
---|
106 | .PP |
---|
107 | .RS +3 |
---|
108 | \fB-f |
---|
109 | \fR |
---|
110 | .RE |
---|
111 | .RS +9 |
---|
112 | Forces the unmount to take place even though the file system may be still |
---|
113 | in use. |
---|
114 | .PP |
---|
115 | Use this flag with \fIextreme caution\fR. Using this flag may |
---|
116 | cause outstanding write operations to be lost. Because of this, forcing |
---|
117 | an unmount can cause data integrity failures and should be used with |
---|
118 | caution. |
---|
119 | .RE |
---|
120 | .PP |
---|
121 | .RS +3 |
---|
122 | \fB-C {all_remote | \fIClusterName\fR} |
---|
123 | \fR |
---|
124 | .RE |
---|
125 | .RS +9 |
---|
126 | Specifies the cluster on which the file system is to be |
---|
127 | force-unmounted. all_remote denotes all clusters other than the one |
---|
128 | from which the command was issued. |
---|
129 | .RE |
---|
130 | .PP |
---|
131 | .RS +3 |
---|
132 | \fB-N {\fINode\fR[,\fINode\fR...] | |
---|
133 | \fINodeFile\fR | \fINodeClass\fR} |
---|
134 | \fR |
---|
135 | .RE |
---|
136 | .RS +9 |
---|
137 | Specifies the nodes on which the file system is to be unmounted. |
---|
138 | .PP |
---|
139 | This command does not support a \fINodeClass\fR of |
---|
140 | \fBmount\fR. |
---|
141 | .PP |
---|
142 | When the \fB-N\fR parameter is specified in conjunction with |
---|
143 | \fB-C\fR \fIClusterName\fR, the specified node names are assumed |
---|
144 | to refer to nodes that belong to the specified remote cluster (as identified |
---|
145 | by the \fBmmlsmount\fR command). The \fBmmumount\fR command |
---|
146 | cannot verify the accuracy of this information. \fINodeClass\fR and |
---|
147 | \fINodeFile\fR are not supported in conjunction with the \fB-C\fR |
---|
148 | option. |
---|
149 | .RE |
---|
150 | .SH "Exit status" |
---|
151 | .PP |
---|
152 | .PP |
---|
153 | .RS +3 |
---|
154 | \fB0 |
---|
155 | \fR |
---|
156 | .RE |
---|
157 | .RS +9 |
---|
158 | Successful completion. |
---|
159 | .RE |
---|
160 | .PP |
---|
161 | .RS +3 |
---|
162 | \fBnonzero |
---|
163 | \fR |
---|
164 | .RE |
---|
165 | .RS +9 |
---|
166 | A failure has occurred. |
---|
167 | .RE |
---|
168 | .SH "Security" |
---|
169 | .PP |
---|
170 | You must have root authority to run the \fBmmumount\fR command. |
---|
171 | .PP |
---|
172 | You may issue the \fBmmumount\fR command from any node in the GPFS |
---|
173 | cluster. |
---|
174 | .SH "Examples" |
---|
175 | .RS +3 |
---|
176 | .HP 3 |
---|
177 | 1. To unmount file system \fBfs1\fR on all nodes in the cluster, issue |
---|
178 | this command: |
---|
179 | .sp |
---|
180 | .nf |
---|
181 | mmumount fs1 -a |
---|
182 | .fi |
---|
183 | .sp |
---|
184 | The system displays output similar to: |
---|
185 | .sp |
---|
186 | .nf |
---|
187 | Fri Feb 10 15:51:25 EST 2006: mmumount: Unmounting file systems ... |
---|
188 | .fi |
---|
189 | .sp |
---|
190 | .HP 3 |
---|
191 | 2. To force unmount file system \fBfs2\fR on the local node, issue this |
---|
192 | command: |
---|
193 | .sp |
---|
194 | .nf |
---|
195 | mmumount fs2 -f |
---|
196 | .fi |
---|
197 | .sp |
---|
198 | The system displays output similar to: |
---|
199 | .sp |
---|
200 | .nf |
---|
201 | Fri Feb 10 15:52:20 EST 2006: mmumount: Unmounting file systems ... |
---|
202 | forced unmount of /fs2 |
---|
203 | .fi |
---|
204 | .sp |
---|
205 | .RE |
---|
206 | .SH "See also" |
---|
207 | .PP |
---|
208 | mmmount Command |
---|
209 | .PP |
---|
210 | mmlsmount Command |
---|
211 | .SH "Location" |
---|
212 | .PP |
---|
213 | \fB/usr/lpp/mmfs/bin\fR |
---|