1 | .TH mmchpolicy 12/01/06 |
---|
2 | mmchpolicy Command |
---|
3 | .SH "Name" |
---|
4 | .PP |
---|
5 | \fBmmchpolicy\fR - Establish policy rules for a GPFS file |
---|
6 | system. |
---|
7 | .SH "Synopsis" |
---|
8 | .PP |
---|
9 | \fBmmchpolicy\fR \fIDevice\fR \fIPolicyFileName\fR \fB[-t \fR |
---|
10 | \fIDescriptiveName\fR \fB] [-I {\fR\fB\fIyes\fR\fR\fB | test} ]\fR |
---|
11 | .SH "Description" |
---|
12 | .PP |
---|
13 | Use the \fBmmchpolicy\fR command to establish the rules for policy-based |
---|
14 | lifecycle management of the files in a given GPFS file system. Some of |
---|
15 | the things that can be controlled with the help of policy rules are: |
---|
16 | .RS +3 |
---|
17 | .HP 3 |
---|
18 | \(bu File placement at creation time |
---|
19 | .HP 3 |
---|
20 | \(bu Replication factors |
---|
21 | .HP 3 |
---|
22 | \(bu Movement of data between storage pools |
---|
23 | .HP 3 |
---|
24 | \(bu File deletion |
---|
25 | .RE |
---|
26 | .PP |
---|
27 | The \fBmmapplypolicy\fR command must be run to move data between |
---|
28 | storage pools or delete files. |
---|
29 | .PP |
---|
30 | Policy changes take effect immediately on all nodes that have the affected |
---|
31 | file system mounted. For nodes that do not have the file system |
---|
32 | mounted, policy changes take effect upon the next mount of the file |
---|
33 | system. |
---|
34 | .PP |
---|
35 | For information on GPFS policies, see the chapter \fIPolicy-based |
---|
36 | data management for GPFS\fR in \fIGeneral Parallel File System: |
---|
37 | Advanced Administration Guide\fR. |
---|
38 | .SH "Parameters" |
---|
39 | .PP |
---|
40 | .RS +3 |
---|
41 | \fB\fIDevice\fR |
---|
42 | \fR |
---|
43 | .RE |
---|
44 | .RS +9 |
---|
45 | The device name of the file system for which policy information is to be |
---|
46 | established or changed. File system names need not be |
---|
47 | fully-qualified. \fBfs0\fR is just as acceptable as |
---|
48 | \fB/dev/fs0\fR. This must be the first parameter. |
---|
49 | .RE |
---|
50 | .PP |
---|
51 | .RS +3 |
---|
52 | \fB\fIPolicyFileName\fR |
---|
53 | \fR |
---|
54 | .RE |
---|
55 | .RS +9 |
---|
56 | The name of the file containing the policy rules. If you specify |
---|
57 | \fBDEFAULT\fR, GPFS replaces the current policy file with a single policy |
---|
58 | rule that assigns all newly created files to the system storage pool. |
---|
59 | .RE |
---|
60 | .SH "Options" |
---|
61 | .PP |
---|
62 | .RS +3 |
---|
63 | \fB-I {\fB\fIyes\fR\fR | test} |
---|
64 | \fR |
---|
65 | .RE |
---|
66 | .RS +9 |
---|
67 | Specifies whether to activate the rules in the policy file |
---|
68 | \fIPolicyFileName\fR. |
---|
69 | .PP |
---|
70 | .RS +3 |
---|
71 | \fByes |
---|
72 | \fR |
---|
73 | .RE |
---|
74 | .RS +9 |
---|
75 | The policy rules are validated and immediately activated. This is |
---|
76 | the default. |
---|
77 | .RE |
---|
78 | .PP |
---|
79 | .RS +3 |
---|
80 | \fBtest |
---|
81 | \fR |
---|
82 | .RE |
---|
83 | .RS +9 |
---|
84 | The policy rules are validated, but not installed. |
---|
85 | .RE |
---|
86 | .RE |
---|
87 | .PP |
---|
88 | .RS +3 |
---|
89 | \fB-t \fIDescriptiveName\fR |
---|
90 | \fR |
---|
91 | .RE |
---|
92 | .RS +9 |
---|
93 | Specifies an optional descriptive name to be associated with the policy |
---|
94 | rules. The string must be less than 256 characters in length. If |
---|
95 | not specified, the descriptive name defaults to the base name portion of the |
---|
96 | \fIPolicyFileName\fR parameter. |
---|
97 | .RE |
---|
98 | .SH "Exit status" |
---|
99 | .PP |
---|
100 | .PP |
---|
101 | .RS +3 |
---|
102 | \fB0 |
---|
103 | \fR |
---|
104 | .RE |
---|
105 | .RS +9 |
---|
106 | Successful completion. |
---|
107 | .RE |
---|
108 | .PP |
---|
109 | .RS +3 |
---|
110 | \fBnonzero |
---|
111 | \fR |
---|
112 | .RE |
---|
113 | .RS +9 |
---|
114 | A failure has occurred. |
---|
115 | .RE |
---|
116 | .SH "Security" |
---|
117 | .PP |
---|
118 | You must have root authority to run the \fBmmchpolicy\fR command. |
---|
119 | .PP |
---|
120 | You may issue the \fBmmchpolicy\fR command from any node in the GPFS |
---|
121 | cluster. |
---|
122 | .SH "Examples" |
---|
123 | .RS +3 |
---|
124 | .HP 3 |
---|
125 | 1. This command validates a policy before it is installed: |
---|
126 | .sp |
---|
127 | .nf |
---|
128 | mmchpolicy fs2 policyfile -I test |
---|
129 | .fi |
---|
130 | .sp |
---|
131 | The system displays output similar to: |
---|
132 | .sp |
---|
133 | .nf |
---|
134 | Validated policy 'policyfile': parsed 3 StgPoolRules, |
---|
135 | 3 MigratRules |
---|
136 | .fi |
---|
137 | .sp |
---|
138 | .HP 3 |
---|
139 | 2. This command installs a policy: |
---|
140 | .sp |
---|
141 | .nf |
---|
142 | mmchpolicy fs2 policyfile |
---|
143 | .fi |
---|
144 | .sp |
---|
145 | The system displays output similar to: |
---|
146 | .sp |
---|
147 | .nf |
---|
148 | Policy 'policyfile' installed and broadcast to all nodes. |
---|
149 | Validated policy 'policyfile': parsed 3 StgPoolRules, |
---|
150 | 3 MigratRules |
---|
151 | .fi |
---|
152 | .sp |
---|
153 | .sp |
---|
154 | To confirm the change, issue this command: |
---|
155 | .sp |
---|
156 | .nf |
---|
157 | mmlspolicy fs2 |
---|
158 | .fi |
---|
159 | .sp |
---|
160 | .sp |
---|
161 | The system displays output similar to: |
---|
162 | .sp |
---|
163 | .nf |
---|
164 | Policy file for file system '/dev/fs2': |
---|
165 | Installed by root@k155n11.kgn.ibm.com on Mon Dec 12 |
---|
166 | 16:56:31 2005. |
---|
167 | First line from original file 'policyfile' was: |
---|
168 | /* This is the policy for the fs2 GPFS file system. */ |
---|
169 | .fi |
---|
170 | .sp |
---|
171 | .RE |
---|
172 | .SH "See also" |
---|
173 | .PP |
---|
174 | mmapplypolicy Command |
---|
175 | .PP |
---|
176 | mmlspolicy Command |
---|
177 | .SH "Location" |
---|
178 | .PP |
---|
179 | \fB/usr/lpp/mmfs/bin\fR |
---|