source: gpfs_3.1_ker2.6.20/share/man/man8/mmremotefs.8 @ 50

Last change on this file since 50 was 16, checked in by rock, 17 years ago
File size: 4.9 KB
Line 
1.TH mmremotefs 02/16/06
2mmremotefs Command
3.SH "Name"
4.PP
5\fBmmremotefs\fR - Manages the information about GPFS file systems
6from other clusters that this cluster can mount.
7.SH "Synopsis"
8.PP
9\fBmmremotefs\fR \fBadd\fR \fIDevice\fR \fB-f\fR
10\fIRemoteDevice\fR \fB-C\fR \fIRemoteClusterName\fR \fB-T\fR
11\fIMountPoint\fR [\fB-A {yes | \fR\fB\fIno\fR\fR\fB |
12automount}\fR] [\fB-o\fR \fIMountOptions\fR]
13.PP
14Or,
15.PP
16\fBmmremotefs\fR \fBdelete {\fR\fIDevice\fR\fB | all | \fR
17\fB-C\fR \fIRemoteClusterName\fR\fB}\fR
18.PP
19Or,
20.PP
21\fBmmremotefs\fR \fBshow\fR [\fIDevice\fR\fB | all |
22\fR\fB-C\fR \fIRemoteClusterName\fR]
23.PP
24Or,
25.PP
26\fBmmremotefs\fR \fBupdate\fR \fIDevice\fR [\fB-f\fR
27\fIRemoteDevice\fR] [\fB-C\fR \fIRemoteClusterName\fR]
28[\fB-T\fR \fIMountPoint\fR] [\fB-A {yes | \fR\fB\fIno\fR\fR\fB | automount}\fR] [\fB-o\fR
29\fIMountOptions\fR]
30.SH "Description"
31.PP
32The \fBmmremotefs\fR command is used to make GPFS file systems that
33belong to other GPFS clusters known to the nodes in this cluster, and to
34maintain the attributes associated with these file systems. The keyword
35appearing after \fBmmremotefs\fR determines which action is
36performed:
37.PP
38.RS +3
39\fBadd
40\fR
41.RE
42.RS +9
43Define a new remote GPFS file system.
44.RE
45.PP
46.RS +3
47\fBdelete
48\fR
49.RE
50.RS +9
51Delete the information for a remote GPFS file system.
52.RE
53.PP
54.RS +3
55\fBshow
56\fR
57.RE
58.RS +9
59Display the information associated with a remote GPFS file system.
60.RE
61.PP
62.RS +3
63\fBupdate
64\fR
65.RE
66.RS +9
67Update the information associated with a remote GPFS file system.
68.RE
69.PP
70Use the \fBmmremotefs\fR command to make the nodes in this cluster aware
71of file systems that belong to other GPFS clusters. The cluster that
72owns the given file system must have already been defined with the \fBmmremotecluster\fR command. The
73\fBmmremotefs\fR command is used to assign a local name under which the
74remote file system will be known in this cluster, the mount point where the
75file system is to be mounted in this cluster, and any local mount options that
76you may want.
77.PP
78Once a remote file system has been successfully defined and a local device
79name associated with it, you can issue normal commands using that local name,
80the same way you would issue them for file systems that are owned by this
81cluster.
82.SH "Parameters"
83.PP
84.RS +3
85\fB\fIDevice\fR
86\fR
87.RE
88.RS +9
89Specifies the name by which the remote GPFS file system will be known in
90the cluster.
91.RE
92.PP
93.RS +3
94\fB-C \fIRemoteClusterName\fR
95\fR
96.RE
97.RS +9
98Specifies the name of the GPFS cluster that owns the remote GPFS file
99system.
100.RE
101.PP
102.RS +3
103\fB-f \fIRemoteDevice\fR
104\fR
105.RE
106.RS +9
107Specifies the actual name of the remote GPFS file system. This is
108the device name of the file system as known to the remote cluster that owns
109the file system.
110.RE
111.SH "Options"
112.PP
113.RS +3
114\fB-A {yes | \fB\fIno\fR\fR | automount}
115\fR
116.RE
117.RS +9
118Indicates when the file system is to be mounted:
119.PP
120.RS +3
121\fByes
122\fR
123.RE
124.RS +9
125When the GPFS daemon starts.
126.RE
127.PP
128.RS +3
129\fBno
130\fR
131.RE
132.RS +9
133Manual mount. This is the default.
134.RE
135.PP
136.RS +3
137\fBautomount
138\fR
139.RE
140.RS +9
141When the file system is first accessed.
142.RE
143.RE
144.PP
145.RS +3
146\fB-o \fIMountOptions\fR
147\fR
148.RE
149.RS +9
150Specifies the mount options to pass to the mount command when mounting the
151file system. For a detailed description of the available mount options,
152see \fIGPFS-specific mount options\fR in \fIGPFS: Administration and Programming Reference\fR.
153.RE
154.PP
155.RS +3
156\fB-T \fIMountPoint\fR
157\fR
158.RE
159.RS +9
160Indicates the local mount point for the remote GPFS file system.
161.RE
162.SH "Exit status"
163.PP
164.PP
165.RS +3
166\fB0
167\fR
168.RE
169.RS +9
170Successful completion. After successful completion of the
171\fBmmremotefs\fR command, the new configuration information is propagated
172to all nodes in the cluster.
173.RE
174.PP
175.RS +3
176\fBnonzero
177\fR
178.RE
179.RS +9
180A failure has occurred.
181.RE
182.SH "Security"
183.PP
184You must have root authority to run the \fBmmremotefs\fR command.
185.PP
186You may issue the \fBmmremotefs\fR command from any node in the GPFS
187cluster.
188.SH "Examples"
189.PP
190This command adds remote file system \fBgpfsn\fR, owned by remote
191cluster \fBk164.kgn.ibm.com\fR, to the local cluster,
192assigning \fBrgpfsn\fR as the local name for the file system, and
193\fB/gpfs/rgpfsn\fR as the local mount point.
194.sp
195.nf
196mmremotefs add rgpfsn -f gpfsn -C k164.kgn.ibm.com -T /gpfs/rgpfsn
197.fi
198.sp
199.PP
200The output is similar to this:
201.sp
202.nf
203mmremotefs: 6027-1371 Propagating the changes to all affected
204                      nodes. This is an asynchronous process.
205.fi
206.sp
207.PP
208The \fBmmremotefs show\fR command can be used to see the changes.
209.sp
210.nf
211mmremotefs show rgpfsn
212.fi
213.sp
214.PP
215The output is similar to this:
216.sp
217.nf
218Local Name  Remote Name Cluster name  Mount Point Mount Options Automount
219rgpfsn      gpfsn      k164n.kgn.ibm.com   /gpfs/rgpfsn rw,mtime,noatime no
220.fi
221.sp
222.SH "See also"
223.PP
224mmauth Command
225.PP
226mmremotecluster Command
227.PP
228\fIAccessing GPFS file systems from other
229GPFS clusters\fR in
230\fIGeneral Parallel
231File System: Advanced Administration Guide\fR.
232.SH "Location"
233.PP
234\fB/usr/lpp/mmfs/bin\fR
235.PP
Note: See TracBrowser for help on using the repository browser.