source: gpfs_3.1_ker2.6.20/share/man/man8/mmsnapdir.8 @ 90

Last change on this file since 90 was 16, checked in by rock, 17 years ago
File size: 5.2 KB
Line 
1.TH mmsnapdir 12/04/06
2mmsnapdir Command
3.SH "Name"
4.PP
5\fBmmsnapdir\fR - Creates and deletes invisible directories that connect to
6the snapshots of a GPFS file system, and changes the name of the snapshots
7subdirectory.
8.SH "Synopsis"
9.PP
10\fBmmsnapdir\fR \fIDevice\fR {[\fB-r\fR | \fB-a\fR]
11[\fB-s\fR \fISnapDirName\fR]}
12.PP
13Or,
14.PP
15\fBmmsnapdir\fR \fIDevice\fR [\fB-q\fR]
16.SH "Description"
17.PP
18Use the \fBmmsnapdir\fR command to create or delete invisible
19directories that connect to the snapshots of a GPFS file system, and change
20the name of the snapshots subdirectory.
21.PP
22Snapshots appear in a subdirectory in the root directory of the file
23system. If you prefer to access the snapshots from each file system
24directory rather than traversing through the root directory, you may create an
25invisible directory to make the connection by issuing the \fBmmsnapdir\fR
26command with the \fB-a\fR flag (see Example 1). The \fB-a\fR flag of the \fBmmsnapdir\fR
27command creates an invisible directory in each normal directory in the active
28file system (they do not appear in directories in snapshots) that contains a
29subdirectory for each existing snapshot of the file system. These
30subdirectories correspond to the copy of the that directory in the snapshot
31with the same name.
32.PP
33If the \fBmmsnapdir\fR command is issued while another snapshot command
34is running, the \fBmmsnapdir\fR command waits for that command to
35complete.
36.PP
37For more information about GPFS snapshots, see \fICreating and maintaining
38snapshots of GPFS file systems\fR in \fIGeneral Parallel File
39System: Advanced Administration Guide\fR.
40.SH "Parameters"
41.PP
42.RS +3
43\fB\fIDevice\fR
44\fR
45.RE
46.RS +9
47The device name of the file system. File system names need not be
48fully-qualified. \fBfs0\fR is just as acceptable as
49\fB/dev/fs0\fR.
50.PP
51This must be the first parameter.
52.RE
53.SH "Options"
54.PP
55.PP
56.RS +3
57\fB-a
58\fR
59.RE
60.RS +9
61Adds a snapshots subdirectory to all subdirectories in the file
62system.
63.RE
64.PP
65.RS +3
66\fB-q
67\fR
68.RE
69.RS +9
70Displays current settings, if issued without any other flags.
71.RE
72.PP
73.RS +3
74\fB-r
75\fR
76.RE
77.RS +9
78Reverses the effect of the \fB-a\fR option. All invisible
79snapshot directories are removed. The snapshot directory under the file
80system root directory is not affected.
81.RE
82.PP
83.RS +3
84\fB-s \fISnapDirName\fR
85\fR
86.RE
87.RS +9
88Changes the name of the snapshots subdirectory to
89\fISnapDirName\fR. This affects both the directory in the file
90system root as well as the invisible directory in the other file system
91directories if the \fBmmsnapdir -a\fR command has been issued.
92.RE
93.SH "Exit status"
94.PP
95.PP
96.RS +3
97\fB0
98\fR
99.RE
100.RS +9
101Successful completion.
102.RE
103.PP
104.RS +3
105\fBnonzero
106\fR
107.RE
108.RS +9
109A failure has occurred.
110.RE
111.SH "Security"
112.PP
113If you are a root user, you may issue the \fBmmsnapdir\fR command from
114any node in the GPFS cluster.
115.PP
116You must be a root user to use the \fB-a\fR, \fB-r\fR,
117and \fB-s\fR options.
118.PP
119If you are a non-root user, you may only specify file systems that
120belong to the same cluster as the node on which the \fBmmsnapdir\fR command
121was issued.
122.PP
123When using the \fBrcp\fR and \fBrsh\fR commands for remote
124communication, a properly configured \fB.rhosts\fR file must exist
125in the root user's home directory on each node in the GPFS
126cluster. If you have designated the use of a different remote
127communication program on either the \fBmmcrcluster\fR or the
128\fBmmchcluster\fR command, you must ensure:
129.RS +3
130.HP 3
1311. Proper authorization is granted to all nodes in the GPFS cluster.
132.HP 3
1332. The nodes in the GPFS cluster can communicate without the use of a
134password, and without any extraneous messages.
135.RE
136.SH "Examples"
137.RS +3
138.HP 3
1391. To rename the \fB.snapshots\fR directory (the
140default snapshots directory name) to \fB.link\fR for file system
141\fBfs1\fR, issue the command:
142.sp
143.nf
144mmsnapdir  fs1 -s .link
145.fi
146.sp
147.sp
148After the command has been issued, the directory structure would appear
149similar to:
150.sp
151.nf
152/fs1/file1
153/fs1/userA/file2
154/fs1/userA/file3
155/fs1/.link/snap1/file1
156/fs1/.link/snap1/userA/file2
157/fs1/.link/snap1/userA/file3
158.fi
159.sp
160.HP 3
1612. Issuing:
162.sp
163.nf
164mmsnapdir fs1 -a
165.fi
166.sp
167After the command has been issued, the directory structure would appear
168similar to:
169.sp
170.nf
171/fs1/file1
172/fs1/userA/file2
173/fs1/userA/file3
174/fs1/userA/.link/snap1/file2
175/fs1/userA/.link/snap1/file3
176/fs1/.link/snap1/file1
177/fs1/.link/snap1/userA/file2
178/fs1/.link/snap1/userA/file3
179.fi
180.sp
181.sp
182The \fB.link\fR subdirectory under the root directory and under
183each subdirectory of the tree provides two different paths to each snapshot
184copy of a file. For example,
185\fB/fs1/userA/.link/snap1/file2\fR and
186\fB/fs1/.link/snap1/userA/file2\fR are two different paths that
187access the same snapshot copy of \fB/fs1/userA/file2\fR.
188.HP 3
1893. Issuing:
190.sp
191.nf
192mmsnapdir fs1 -r
193.fi
194.sp
195After the command has been issued, the directory structure would appear
196similar to:
197.sp
198.nf
199/fs1/file1
200/fs1/userA/file2
201/fs1/userA/file3
202/fs1/.link/snap1/file1
203/fs1/.link/snap1/userA/file2
204/fs1/.link/snap1/userA/file3
205.fi
206.sp
207.HP 3
2084. Issuing:
209.sp
210.nf
211mmsnapdir fs1 -q
212.fi
213.sp
214The output is similar to this:
215.sp
216.nf
217Snapshot directory for "fs1" is ".link" (root directory only)
218.fi
219.sp
220.RE
221.SH "See also"
222.PP
223mmcrsnapshot Command
224.PP
225mmdelsnapshot Command
226.PP
227mmlssnapshot Command
228.PP
229mmrestorefs Command
230.SH "Location"
231.PP
232\fB/usr/lpp/mmfs/bin\fR
Note: See TracBrowser for help on using the repository browser.